Triple
T13358544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 100 |
E318758
|
entity |
| Predicate | isLandmarkEvent |
P109610
|
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 100, isLandmarkEvent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLandmarkEvent Context triple: [UFC 100, isLandmarkEvent, true]
-
A.
isLandmarkFor
Indicates that one entity serves as a notable or significant reference point or attraction for another entity, such as a place, route, or area.
-
B.
includesLandmark
Indicates that one location or area contains or encompasses a specific landmark within its boundaries.
-
C.
isLandmarkAlbumReleaseFor
Indicates that an album release is widely recognized as a pivotal, highly influential, or defining milestone in the career, genre, or history associated with the referenced entity.
-
D.
isLandmarkResultIn
Indicates that something serves as a landmark within, or as a result associated with, a particular context, area, or entity.
-
E.
isLocalLandmark
Indicates that something is recognized as a notable or significant landmark within a specific local area or community.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69da62887e588190bd7241c720a112a2 |
completed | April 11, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69d9a02c9abc8190b328e7bae747bfc5 |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadcce5a808190847f2a7833b67a5a |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:32 p.m.