Triple
T13530104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phaeophyceae |
E323109
|
entity |
| Predicate | bodyOrganization |
P110720
|
FINISHED |
| Object | mostly multicellular |
—
|
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: mostly multicellular | Statement: [Phaeophyceae, bodyOrganization, mostly multicellular]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyOrganization Context triple: [Phaeophyceae, bodyOrganization, mostly multicellular]
-
A.
organLocation
Indicates the anatomical location or position of an organ within a body or organism.
-
B.
subjectOrganization
Indicates that one entity serves as the organization to which another entity (such as a person, work, or activity) is affiliated or belongs.
-
C.
associatedOrgan
Indicates that one entity has a relevant connection or linkage to a particular organ, such as anatomical, functional, or pathological association.
-
D.
mainOrganOf
Indicates that one entity is the primary or central organ responsible for the core functions of another entity (such as an organism or system).
-
E.
reportingBody
Indicates the entity that is responsible for providing or submitting a report about another entity or event.
- F. None of above. chosen
Provenance (4 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafba2c308190873efd15dfe26358 |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbaecc98cc8190829f5be759c4f1e3 |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:44 p.m.