Triple
T10640190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osteoglossum bicirrhosum |
E250698
|
entity |
| Predicate | bodyPosition |
P91855
|
FINISHED |
| Object | surface-oriented |
—
|
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: surface-oriented | Statement: [Osteoglossum bicirrhosum, bodyPosition, surface-oriented]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyPosition Context triple: [Osteoglossum bicirrhosum, bodyPosition, surface-oriented]
-
A.
positionB
Indicates that one entity occupies or is located at a specific position relative to another entity.
-
B.
positionHead
Indicates that one entity serves as the head or primary governing element in the positional or syntactic structure of another entity.
-
C.
bearerPosition
Indicates the spatial or positional relationship of a bearer (holder or carrier) relative to the item or entity it bears.
-
D.
locationPosed
chosen
Indicates that an entity is positioned or situated at a specific location.
-
E.
bodyState
Indicates the physical condition or status that an entity’s body is currently in.
- 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dfcbe5308190986bba438d19e852 |
completed | April 8, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69d6dd83b114819098e84dc658e82d7e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:04 p.m.