Triple
T16211773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brachiopoda |
E393482
|
entity |
| Predicate | shellOrientation |
P40589
|
FINISHED |
| Object | dorsal-ventral hinge |
—
|
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: dorsal-ventral hinge | Statement: [Brachiopoda, shellOrientation, dorsal-ventral hinge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shellOrientation Context triple: [Brachiopoda, shellOrientation, dorsal-ventral hinge]
-
A.
sessionOrientation
Indicates the directional or spatial alignment relationship established between entities within a session or interaction context.
-
B.
bellOrientation
Indicates the spatial direction or alignment in which a bell is positioned or facing.
-
C.
surfaceOrientation
chosen
Indicates the spatial orientation or facing direction of a surface relative to a reference frame or viewpoint.
-
D.
pouchOrientation
Indicates the spatial direction or alignment of a pouch relative to a reference frame or object.
-
E.
performanceOrientation
Indicates a relationship where an entity is characterized by a focus on achieving high performance, results, or measurable outcomes in its activities or behavior.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e227f1bef8819094e724f5cd0b86d5 |
completed | April 17, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.