Triple
T5112514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intimate Relations |
E115248
|
entity |
| Predicate | featuresOrganisms |
P5692
|
FINISHED |
| Object | invertebrates |
—
|
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: invertebrates | Statement: [Intimate Relations, featuresOrganisms, invertebrates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresOrganisms Context triple: [Intimate Relations, featuresOrganisms, invertebrates]
-
A.
featuresSpecies
Indicates that something includes, presents, or highlights a particular species as part of its content or composition.
-
B.
targetOrganism
Indicates that an action, process, or effect is directed toward or intended to impact a particular organism.
-
C.
faunaCharacteristic
chosen
Indicates that an entity has a specific trait, feature, or quality related to animals or animal life.
-
D.
biologicalCharacteristic
Indicates that one entity possesses or exhibits a particular biological trait, feature, or property in relation to another.
-
E.
featuresHabitat
Indicates that something includes or provides a particular habitat as part of its characteristics or environment.
- 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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75ca57e881908242def2a032902e |
completed | March 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69bd715fe3a8819087d3065adddba515 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:41 p.m.