Triple
T35690758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ison system |
E1031281
|
entity |
| Predicate | sharesSectorWith |
P202290
|
FINISHED |
| Object | Hoth system |
—
|
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: Hoth system | Statement: [Ison system, sharesSectorWith, Hoth system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesSectorWith Context triple: [Ison system, sharesSectorWith, Hoth system]
-
A.
sharesMarketWith
Indicates that two entities operate in or target the same market or customer segment, implying competitive or overlapping commercial presence.
-
B.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
C.
sharesQuestWith
Indicates that two or more entities are participating in, or have access to, the same quest or mission.
-
D.
sharesModuleWith
Indicates that two entities are associated with or participate in at least one common module.
-
E.
sharesDivisionWith
Indicates that two entities belong to or operate within the same organizational division.
- 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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a006ef900148190ba52daf566882a03 |
completed | May 10, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_6a006c76ae748190bfe466d7d17d321e |
completed | May 10, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_6a006ef80ce88190b5e3a2b261409d44 |
completed | May 10, 2026, 11:41 a.m. |
Created at: May 3, 2026, 4:05 p.m.