Triple
T23987477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GAA |
E604977
|
entity |
| Predicate | establishedLine |
P76594
|
FINISHED |
| Object | Israel–Egypt armistice line |
—
|
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: Israel–Egypt armistice line | Statement: [GAA, establishedLine, Israel–Egypt armistice line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedLine Context triple: [GAA, establishedLine, Israel–Egypt armistice line]
-
A.
currentLineEstablished
Indicates that a particular line (such as a route, connection, or communication channel) has been successfully set up and is currently active.
-
B.
connectedLine
Indicates that two entities are joined by a continuous line or linear connection.
-
C.
formedLine
Indicates that an entity has arranged itself or others into a line or linear formation.
-
D.
definedLine
chosen
Indicates that a specific line (such as a boundary, path, or reference line) has been formally established or specified within a given context.
-
E.
associatedLine
Indicates that one entity is linked or connected to a particular line (such as a line item, line of text, or line in a structure) with which it is contextually or functionally related.
- 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_69e295463f7c8190b1c19dbd114641b9 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d38838f481909a52fccd392a92df |
completed | April 29, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:36 p.m.