Triple
T37406843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glanum |
E929154
|
entity |
| Predicate | excavationCountry |
P77363
|
FINISHED |
| Object | France |
—
|
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: France | Statement: [Glanum, excavationCountry, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excavationCountry Context triple: [Glanum, excavationCountry, France]
-
A.
countryAtExcavationTime
chosen
Indicates that a specified location or site was within the borders or jurisdiction of a particular country at the time the excavation took place.
-
B.
excavatedIn
Indicates that something (typically an artifact, structure, or site) was uncovered or dug out during an excavation that took place at a specific time or within a specific time period.
-
C.
countryOfExcavator
Indicates that one entity is the country associated with the excavator (such as the nation where the excavator originates, is registered, or is based) used in relation to the other entity.
-
D.
excavatedAt
Indicates that an excavation activity took place at a specific location or site.
-
E.
excavatedUnder
Indicates that one entity was dug out, uncovered, or removed from beneath another entity during an excavation process.
- 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_69f76ebbf79c8190b85bbcf3a6be57e4 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.