Triple
T937686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Indochina War |
E20232
|
entity |
| Predicate | divisionLine |
P21958
|
FINISHED |
| Object | 17th parallel north |
—
|
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: 17th parallel north | Statement: [First Indochina War, divisionLine, 17th parallel north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divisionLine Context triple: [First Indochina War, divisionLine, 17th parallel north]
-
A.
dividedBetween
Indicates that something is partitioned or shared among two or more distinct entities or groups.
-
B.
divisionTitle
Indicates the formal name or title assigned to a specific division within a larger organization or structure.
-
C.
fieldDivision
Indicates a relationship where a larger field or area is partitioned into smaller sections or subdivisions.
-
D.
lineStandard
Indicates that one entity is a standard or reference specification that defines or governs the characteristics or requirements of a particular line (such as a product line, production line, or service line).
-
E.
division
Indicates a relationship where one entity is separated or partitioned into parts, groups, or sections based on some criterion or operation.
- 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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b388f0bc8190a087222636135ba5 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b29c68f48190aecad10e351a99de |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b344f6f48190ba03ce593c94176b |
completed | March 1, 2026, 9:44 p.m. |
Created at: March 1, 2026, 7:40 p.m.