Triple
T8479232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opisthokonta |
E200472
|
entity |
| Predicate | unitedBy |
P35330
|
FINISHED |
| Object | shared cellular features |
—
|
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: shared cellular features | Statement: [Opisthokonta, unitedBy, shared cellular features]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unitedBy Context triple: [Opisthokonta, unitedBy, shared cellular features]
-
A.
unites
chosen
Indicates that one entity brings together multiple entities into a single, cohesive whole or shared state.
-
B.
endedUnionBetween
Indicates that one entity caused or marked the termination of a union, alliance, or partnership with another entity.
-
C.
reunitedIn
Indicates that entities who were previously separated have come together again at a specific time or place.
-
D.
formedByUnionOf
Indicates that something is created or defined as the union or combination of multiple other things.
-
E.
joinedUNTogetherWith
Indicates that one entity became a member of or affiliated with the University of North Texas together with another entity, at the same time or as part of the same event.
- 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_69ca831b17988190a1f3f3413d57b820 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe5232d008190ae55b982f5fc9e8b |
completed | March 31, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69cbd104250c8190b4c499dcc9937494 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:12 p.m.