Triple
T36954504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack of Blades |
E914153
|
entity |
| Predicate | finalForm |
P86650
|
FINISHED |
| Object | dragon |
—
|
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: dragon | Statement: [Jack of Blades, finalForm, dragon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalForm Context triple: [Jack of Blades, finalForm, dragon]
-
A.
finaleForm
chosen
Indicates that one entity represents the final or ultimate form, version, or stage of another entity.
-
B.
nonFinalForm
Indicates that an entity (such as a character, token, or form) appears in a non-final position or uses a non-final variant within a sequence or word.
-
C.
finalSubmissionType
Indicates the specific category or format of the last or definitive version submitted in a process or workflow.
-
D.
finalStep
Indicates that an action or state represents the last step or concluding stage in a process or sequence.
-
E.
finalRecord
Indicates that a record represents the last or ultimate version/state in a sequence or process.
- 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fef112398081909237c3872345968b |
completed | May 9, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69feefb14ec08190ab401987d8c84a23 |
completed | May 9, 2026, 8:26 a.m. |
Created at: May 3, 2026, 4:13 p.m.