Triple
T4459950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nephrozoa |
E98226
|
entity |
| Predicate | hasGermLayers |
P18574
|
FINISHED |
| Object | ectoderm |
—
|
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: ectoderm | Statement: [Nephrozoa, hasGermLayers, ectoderm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGermLayers Context triple: [Nephrozoa, hasGermLayers, ectoderm]
-
A.
germLayers
chosen
Indicates the developmental relationship between an organism or structure and the embryonic germ layers (ectoderm, mesoderm, endoderm) from which it originates.
-
B.
hasGenerations
Indicates a relationship where an entity is associated with one or more successive generational levels or cohorts derived from it.
-
C.
hasNotableLineage
Indicates that an entity descends from, or is associated with, a distinguished or historically significant family, ancestry, or heritage.
-
D.
hasLateralStructure
Indicates that one entity possesses or exhibits a structural feature oriented to or located on its side(s).
-
E.
hasLarvalFeature
Indicates that an entity possesses a characteristic or trait specifically associated with its larval developmental stage.
- 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_69b3454a7c608190944f5455c8031d73 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35673337c8190b923159791ec27e3 |
completed | March 13, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69b34f649df081909d3cc2f6a1b8f282 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:33 p.m.