Triple
T3653674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asymmetron |
E77478
|
entity |
| Predicate | notochord |
P15765
|
FINISHED |
| Object | present |
—
|
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: present | Statement: [Asymmetron, notochord, present]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notochord Context triple: [Asymmetron, notochord, present]
-
A.
adultNotochord
chosen
Indicates that the organism retains a notochord as an adult, rather than only during embryonic or larval stages.
-
B.
adultDorsalNerveCord
Indicates that one entity has, forms, or constitutes the dorsal nerve cord in its adult developmental stage in relation to another entity or context.
-
C.
coelomFormation
Indicates the developmental process by which a true body cavity (coelom) forms within an organism’s embryonic tissues.
-
D.
embryologicalFeature
Indicates a relationship where one entity is an anatomical or biological structure characterized or defined by its origin, development, or properties during the embryonic stage.
-
E.
swimBladder
Indicates that an entity possesses or is associated with a swim bladder, an internal gas-filled organ used to control buoyancy in water.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3b9164c81908938a4338430d193 |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb84650148190bf79231105e58d7f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.