Triple
T745043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cnidaria |
E15322
|
entity |
| Predicate | hasOrganLevelOrganization |
P18576
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Cnidaria, hasOrganLevelOrganization, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrganLevelOrganization Context triple: [Cnidaria, hasOrganLevelOrganization, false]
-
A.
hasOrganizationalStructure
Indicates that an entity possesses a defined internal arrangement of roles, responsibilities, and relationships that determine how it is organized and operates.
-
B.
includesOrganization
Indicates that one entity contains, encompasses, or has within it the specified organization as a component, member, or part.
-
C.
hasKeyOrganization
Indicates that an entity is associated with or primarily represented by a main or primary organization.
-
D.
hasPositionInOrganization
Indicates that an entity holds a specific role, job, or position within a particular organization.
-
E.
hasMajorOrganization
Indicates that an entity is associated with or primarily represented by a major organization.
- 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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a61217b881908592096b1edacb8a |
completed | March 1, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69a4a4ff10608190bfd60b4a1cb38f7d |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a57267c481909790a1fda3fced08 |
completed | March 1, 2026, 8:45 p.m. |
Created at: March 1, 2026, 7:37 p.m.