Triple
T37456626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terran Dominion |
E930815
|
entity |
| Predicate | notableRebelOpponent |
P107017
|
FINISHED |
| Object | Jim Raynor |
E750226
|
NE 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: Jim Raynor | Statement: [Terran Dominion, notableRebelOpponent, Jim Raynor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRebelOpponent Context triple: [Terran Dominion, notableRebelOpponent, Jim Raynor]
-
A.
rebelsLeader
Indicates that one entity serves as the leader of a group of rebels associated with the other entity.
-
B.
typeOfRebel
Indicates that one entity is a rebel belonging to, or classified under, a particular type or category of rebellion.
-
C.
notableCombatant
Indicates that an entity is recognized as a significant or distinguished participant in a particular conflict or combat event.
-
D.
ImperialCommander
Indicates a relationship where an individual holds a high-ranking command position within an imperial military or governing hierarchy.
-
E.
rebelsAgainst
chosen
Indicates that one entity actively resists, opposes, or rises up against the authority, control, or established order represented by another entity.
- F. None of above.
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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40826588348190a9a7f0a0edf1b210 |
completed | June 28, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.