Triple
T6518778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1949 Armistice Agreements |
E148327
|
entity |
| Predicate | mapColorOrigin |
P53192
|
FINISHED |
| Object | Green Line named for green ink used on maps |
—
|
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: Green Line named for green ink used on maps | Statement: [1949 Armistice Agreements, mapColorOrigin, Green Line named for green ink used on maps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapColorOrigin Context triple: [1949 Armistice Agreements, mapColorOrigin, Green Line named for green ink used on maps]
-
A.
mapColor
Indicates a relationship where a map region or area is assigned or associated with a specific color, typically for visualization or categorization purposes.
-
B.
mapColorLines
Indicates a relationship where colors are assigned or associated with specific lines, such as mapping each line to a particular color.
-
C.
mapColorLine
Indicates a relationship where a specific color is assigned to or associated with a particular line (such as a route, path, or boundary) on a map.
-
D.
colorOrigin
chosen
Indicates the source or cause from which an entity’s color is derived or determined.
-
E.
mapsFrom
Indicates that one entity is derived, transformed, or constructed based on data, structure, or content originating from 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ac108abc819082d1368af6611a92 |
completed | March 27, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:44 p.m.