Triple
T29017385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sulik |
E737352
|
entity |
| Predicate | coexistsWithSpecies |
P46316
|
FINISHED |
| Object | Nildoror |
—
|
NE NERFINISHED |
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: Nildoror | Statement: [Sulik, coexistsWithSpecies, Nildoror]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coexistsWithSpecies Context triple: [Sulik, coexistsWithSpecies, Nildoror]
-
A.
cohabitsWith
Indicates that two entities live together in the same dwelling or shared residence.
-
B.
hasCommonSpecies
Indicates that two entities share at least one species in common.
-
C.
hasCompanionSpecies
Indicates that one entity is accompanied by, or exists in association with, another entity of a different species.
-
D.
interactionWithOtherSpecies
chosen
Indicates a relationship where an entity engages in some form of contact, influence, or exchange with members of a different species.
-
E.
coFoundingSpeciesWith
Indicates that two species jointly originated, evolved, or established themselves together in a shared context, such as a mutualistic relationship, co-evolutionary history, or simultaneous introduction.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fe190a081909dabf1e185d1575a |
completed | May 2, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:46 a.m.