Triple
T32484273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Compagnie de l’Est |
E830194
|
entity |
| Predicate | servedBorderArea |
P82
|
FINISHED |
| Object | Franco-German border |
—
|
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: Franco-German border | Statement: [Compagnie de l’Est, servedBorderArea, Franco-German border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedBorderArea Context triple: [Compagnie de l’Est, servedBorderArea, Franco-German border]
-
A.
servesBorder
Indicates that one entity functions as a boundary or border for another entity.
-
B.
areaServed
chosen
Indicates the geographic region or jurisdiction within which a service, organization, or activity is provided or applicable.
-
C.
borderArea
Indicates that an area lies along or near the boundary between two regions, countries, or territories.
-
D.
servesRemoteArea
Indicates that an entity provides services or support to people or locations in geographically remote or hard-to-reach areas.
-
E.
nearbyAreaServed
Indicates that a location or entity provides services or coverage to an adjacent or nearby area.
- 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_69f3491ff3b48190b50a7fa00bb05b1f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff29d831b881908d485609e0fc1d0b |
completed | May 9, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_69ff28f9f9e4819087f3402735de66c7 |
completed | May 9, 2026, 12:30 p.m. |
Created at: May 1, 2026, 12:58 a.m.