Triple
T24836307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Les Alyscamps |
E621481
|
entity |
| Predicate | locatedInDepictedPlace |
P24427
|
FINISHED |
| Object | ancient Roman burial ground |
—
|
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: ancient Roman burial ground | Statement: [Les Alyscamps, locatedInDepictedPlace, ancient Roman burial ground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInDepictedPlace Context triple: [Les Alyscamps, locatedInDepictedPlace, ancient Roman burial ground]
-
A.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
B.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
-
C.
placeOfDepiction
chosen
Indicates the location or setting where the depicted subject is shown as being situated in the representation.
-
D.
location depicted
Indicates that one entity visually represents or shows the place where another entity is situated or occurs.
-
E.
locatedInAttractionScene
Indicates that one entity is situated within or is part of the setting or scene of an attraction.
- 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_69e2fac185d48190a0a6073ad1f6b792 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 18, 2026, 5:17 a.m.