Triple
T15343524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ornithischia |
E366857
|
entity |
| Predicate | pubisOrientation |
P79089
|
FINISHED |
| Object | backward-pointing pubis |
—
|
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: backward-pointing pubis | Statement: [Ornithischia, pubisOrientation, backward-pointing pubis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pubisOrientation Context triple: [Ornithischia, pubisOrientation, backward-pointing pubis]
-
A.
pelvicOrientation
chosen
Indicates the spatial alignment or positioning of the pelvis relative to a reference frame or other body parts.
-
B.
coneSex
Indicates a sexual or mating relationship involving a cone-shaped structure or entity.
-
C.
poleOrientation
Indicates the directional alignment or facing of a pole relative to a reference frame or coordinate system.
-
D.
sexualOrientation
Indicates an entity’s enduring pattern of romantic or sexual attraction toward others, typically in terms of the genders or sexes to which it is attracted.
-
E.
legOrientation
Indicates the relative positioning or directional alignment of an entity’s leg(s) with respect to a reference frame or another object.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e163a3c8190ab933411372c1573 |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:17 a.m.