Triple
T7266494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamata no Orochi |
E160986
|
entity |
| Predicate | objectLocation |
P76038
|
FINISHED |
| Object | tail |
—
|
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: tail | Statement: [Yamata no Orochi, objectLocation, tail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: objectLocation Context triple: [Yamata no Orochi, objectLocation, tail]
-
A.
subjectLocation
Indicates that one entity is located at, in, or near the place or position specified by another entity.
-
B.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
C.
locationInSystem
Indicates that one entity is situated within or belongs to the spatial or organizational bounds of a particular system.
-
D.
propertyLocation
Indicates the geographical place or address where a property is situated or found.
-
E.
operationLocation
Indicates the place or site where an operation, activity, or process is carried out.
- 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_69c6885181008190b419040e22939c7c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb088dac8190b353f6ea3d686025 |
completed | March 27, 2026, 8:39 p.m. |
| PD | Predicate disambiguation | batch_69c6e76876608190ac4652bc7153302e |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6eb06acd881908a1735fbbbd5756f |
completed | March 27, 2026, 8:39 p.m. |
Created at: March 27, 2026, 2:58 p.m.