Triple
T22044487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFI's 100 Years...100 Passions |
E544724
|
entity |
| Predicate | listOrderCriterion |
P58213
|
FINISHED |
| Object | most memorable love stories |
—
|
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: most memorable love stories | Statement: [AFI's 100 Years...100 Passions, listOrderCriterion, most memorable love stories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listOrderCriterion Context triple: [AFI's 100 Years...100 Passions, listOrderCriterion, most memorable love stories]
-
A.
sortingOrderSupport
Indicates whether a system or component supports arranging items according to a specified sorting order.
-
B.
orderedBy
Indicates that one entity has placed a request or purchase for another entity, typically specifying who initiated the order.
-
C.
columnOrder
Indicates the relative sequencing or arrangement of columns within a structured layout or dataset.
-
D.
fieldOrder
Indicates the sequence or arrangement in which fields are ordered relative to one another.
-
E.
displayOrder
chosen
Indicates the sequence or position in which items should be presented or shown relative to one another.
- F. None of above.
Provenance (3 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1282d5bb08190849d5084962bf3a5 |
completed | April 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:25 p.m.