Triple
T37539623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Final Fantasy XIV: Heavensward |
E933291
|
entity |
| Predicate | addsJob |
P188222
|
FINISHED |
| Object | Dark Knight |
—
|
NE NERFINISHED |
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: Dark Knight | Statement: [Final Fantasy XIV: Heavensward, addsJob, Dark Knight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsJob Context triple: [Final Fantasy XIV: Heavensward, addsJob, Dark Knight]
-
A.
jobInput
Indicates that one entity serves as an input or required resource for performing or executing a particular job or task involving another entity.
-
B.
addsTrial
Indicates that an entity initiates or includes a trial phase or trial version for another entity.
-
C.
addsQuest
Indicates that one entity assigns or introduces a quest to another entity or into a system.
-
D.
addsUnit
Indicates that one entity increases another by contributing an additional unit or component to it.
-
E.
userTask
Indicates that a specific task is assigned to, owned by, or performed by a particular user.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba5ee00fc81909be7b947a3f95034 |
completed | May 6, 2026, 8:34 p.m. |
Created at: May 3, 2026, 4:17 p.m.