Triple
T25569248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tervate |
E640926
|
entity |
| Predicate | frontLineProximity |
P61842
|
FINISHED |
| Object | close to historic Yser Front |
—
|
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: close to historic Yser Front | Statement: [Tervate, frontLineProximity, close to historic Yser Front]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontLineProximity Context triple: [Tervate, frontLineProximity, close to historic Yser Front]
-
A.
frontLineNear
chosen
Indicates that one entity is located close to the primary boundary or front line associated with another entity.
-
B.
frontLineBetween
Indicates that a boundary or line of direct confrontation exists separating two opposing sides or regions.
-
C.
frontLineReached
Indicates that an entity has arrived at or crossed into the designated front line or primary boundary of engagement.
-
D.
frontLineDuring
Indicates that an entity is positioned at or serves on the front line during a specified time or event.
-
E.
frontLine
Indicates that an entity is positioned at or associated with the foremost or primary line of engagement, activity, or defense relative to others.
- 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_69e75dc281bc819095ec04dc0c3a94d0 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8fedd38819096b4cb0016019b7d |
completed | May 2, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 3:56 p.m.