Triple
T35389323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The 10 Most Fascinating People |
E1022881
|
entity |
| Predicate | numberOfProfilesPerEdition |
P206963
|
FINISHED |
| Object | 10 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 10 | Statement: [The 10 Most Fascinating People, numberOfProfilesPerEdition, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfProfilesPerEdition Context triple: [The 10 Most Fascinating People, numberOfProfilesPerEdition, 10]
-
A.
numberOfEditions
Indicates the total count of distinct editions associated with a given entity.
-
B.
hasDifferentEditions
Indicates that an entity exists in multiple distinct versions or editions that differ in some characteristics.
-
C.
matchCountPerEdition
Indicates the number of matches associated with each specific edition or version of an event, competition, or publication.
-
D.
hasEditionAvailability
Indicates that a particular edition of an item is available in a specified form, location, or channel.
-
E.
hasEditionType
Indicates that one entity is a specific edition type or format classification of another entity (such as a work, publication, or product).
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.