Triple
T35829970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 92 |
E1035768
|
entity |
| Predicate | hasStackedCardReputation |
P201670
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [UFC 92, hasStackedCardReputation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStackedCardReputation Context triple: [UFC 92, hasStackedCardReputation, true]
-
A.
haveReputation
Indicates that an entity is recognized or regarded in a certain way by others, reflecting its perceived character, quality, or status.
-
B.
hasQuirkyReputation
Indicates that an entity is regarded by others as having an unusual, eccentric, or unconventional character or style.
-
C.
hasCollectorReputation
Indicates that an entity holds a recognized status or reputation as a collector, typically based on its history or behavior of collecting items.
-
D.
hasHouseholdReputation
Indicates that an entity holds a particular reputation or standing within a household or among household members.
-
E.
hasViewReputation
Indicates that an entity holds a reputation or recognized standing specifically related to viewing, observing, or accessing something.
- 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_69f76e192a94819082db360cb91e6a8d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00119d821c8190874786391b27ef23 |
completed | May 10, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_6a001143fb6881909ac0ae8bfea04351 |
completed | May 10, 2026, 5:01 a.m. |
| PDg | Predicate description generation | batch_6a00119ca1d881909a72a9c3b937c43c |
completed | May 10, 2026, 5:03 a.m. |
Created at: May 3, 2026, 4:06 p.m.