Triple
T10877834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acanthuroidei |
E256843
|
entity |
| Predicate | tailSpineLocation |
P32348
|
FINISHED |
| Object | caudal peduncle |
—
|
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: caudal peduncle | Statement: [Acanthuroidei, tailSpineLocation, caudal peduncle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tailSpineLocation Context triple: [Acanthuroidei, tailSpineLocation, caudal peduncle]
-
A.
seatOfBody
Indicates that one entity serves as the physical location or base where another entity (typically an organization or authority) is situated or headquartered.
-
B.
locatedAtBaseOf
Indicates that one entity is positioned at or near the bottom or lowest supporting part of another entity.
-
C.
locatedOnBody
chosen
Indicates that one entity is physically situated on the surface or external part of another entity’s body.
-
D.
affectsAnatomicalLocation
Indicates that one entity produces an effect on, or has an impact at, a specific anatomical location.
-
E.
hasSpines
Indicates that one entity possesses or is characterized by spines or spine-like structures.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751ad8cdc819093eafaf12fc23b15 |
completed | April 9, 2026, 7:13 a.m. |
| PD | Predicate disambiguation | batch_69d70d360c388190a3d829fe8862434f |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.