Triple
T32644967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | xXx |
E834573
|
entity |
| Predicate | notableStuntType |
P205129
|
FINISHED |
| Object | extreme sports stunts |
—
|
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: extreme sports stunts | Statement: [xXx, notableStuntType, extreme sports stunts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableStuntType Context triple: [xXx, notableStuntType, extreme sports stunts]
-
A.
notableManeuver
Indicates that an entity is recognized for performing a specific maneuver, action, or tactical move that is considered notable or significant.
-
B.
notableStrike
Indicates that an entity is recognized for having carried out or been involved in a particularly significant or impactful strike (such as a labor strike, military strike, or similar major action).
-
C.
notableAppearanceFeature
Indicates that an entity is characterized by a distinctive or noteworthy physical appearance trait.
-
D.
notableJourneyType
Indicates that there is a particularly significant or noteworthy type of journey associated with the subject.
-
E.
notableStand
Indicates that an entity is particularly well-known or distinguished for a specific stance, position, or viewpoint.
- 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_69f3492e773c81908afc10651e46cad3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037cab06288190b093935f235ddff2 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:07 a.m.