Triple
T33944777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lemonum |
E870259
|
entity |
| Predicate | regionRelativeTo |
P23578
|
FINISHED |
| Object | western Gaul |
—
|
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: western Gaul | Statement: [Lemonum, regionRelativeTo, western Gaul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionRelativeTo Context triple: [Lemonum, regionRelativeTo, western Gaul]
-
A.
regionFrom
Indicates that something originates from, is derived from, or is associated with a particular geographic or administrative region.
-
B.
relativePosition
chosen
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
C.
regionReference
Indicates that one entity refers to, points to, or is associated with a specific region or area defined by another entity.
-
D.
locationRelativeToBorder
Indicates the position or placement of something in relation to a specified border or boundary.
-
E.
relativePositioning
Indicates how one entity is spatially arranged or located in relation to 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff519b65f081909902ba83b775ef85 |
completed | May 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69ff506fccdc8190bd93269589040aed |
completed | May 9, 2026, 3:19 p.m. |
Created at: May 1, 2026, 1:49 a.m.