Triple
T30859473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altius |
E786019
|
entity |
| Predicate | coOccursWith |
P25756
|
FINISHED |
| Object | Citius |
—
|
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: Citius | Statement: [Altius, coOccursWith, Citius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coOccursWith Context triple: [Altius, coOccursWith, Citius]
-
A.
oftenAccompaniedBy
Indicates that one entity is frequently found together with, occurs alongside, or is commonly associated in presence or use with another entity.
-
B.
coexistedWith
Indicates that two entities existed at the same time and in the same context or environment, without implying any specific type of interaction between them.
-
C.
appearsAlongside
chosen
Indicates that two entities are present or occur together in the same context, setting, or instance.
-
D.
occursTo
Indicates that an event, idea, or realization happens in or comes to the mind or awareness of an entity.
-
E.
commonlyLinkedTo
Indicates that one entity is frequently or typically associated, connected, or co-occurring with another entity.
- 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_69f224b91c14819084e764832fe67a57 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f691a7353c8190bf1cf3ead5cc6421 |
completed | May 3, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:46 p.m.