Triple
T35804697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | War Zone |
E1035072
|
entity |
| Predicate | sisterSegment |
P184116
|
FINISHED |
| Object | Raw Is War |
—
|
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: Raw Is War | Statement: [War Zone, sisterSegment, Raw Is War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sisterSegment Context triple: [War Zone, sisterSegment, Raw Is War]
-
A.
sisterChannel
Indicates that one channel is a sibling or counterpart to another channel, typically under the same ownership or network.
-
B.
sisterSubdivision
Indicates that two administrative or organizational subdivisions share a common parent division and are thus parallel or peer units to each other.
-
C.
sisterTerminal
Indicates that two terminals share a sibling-like relationship, typically meaning they are distinct but related endpoints within the same larger system or structure.
-
D.
sisterModule
Indicates that two modules share a common parent or grouping, making them parallel or peer components within the same larger structure.
-
E.
sisterLine
Indicates that one entity is a sister of another within a family or genealogical relationship.
- 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:06 p.m.