Triple
T8552134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Art of Fighting |
E202467
|
entity |
| Predicate | notableForEra |
P561
|
FINISHED |
| Object | early 1990s arcade fighting games |
—
|
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: early 1990s arcade fighting games | Statement: [Art of Fighting, notableForEra, early 1990s arcade fighting games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableForEra Context triple: [Art of Fighting, notableForEra, early 1990s arcade fighting games]
-
A.
notableEra
chosen
Indicates the historical period or era for which an entity is especially recognized or significant.
-
B.
notableEraNickname
Indicates the informal or popular nickname by which a particular historical era or period is commonly known.
-
C.
notableEraTeam2
Indicates that the second team is notably associated with, or prominent during, a particular historical era or period.
-
D.
notableEraStart
Indicates the point in time when a notable or historically significant era associated with an entity begins.
-
E.
notableEraTeam1
Indicates that the first team is notably associated with, or representative of, a particular historical era or period.
- 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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe886fb788190a73e7c76c4f86409 |
completed | March 31, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69cbd113e05c81908f4f3fc1b5925164 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:19 p.m.