Triple
T4577237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonia Julia Firma Secundanorum Arausio |
E123166
|
entity |
| Predicate | hasRemainsIn |
P16216
|
FINISHED |
| Object | historic center of Orange |
—
|
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: historic center of Orange | Statement: [Colonia Julia Firma Secundanorum Arausio, hasRemainsIn, historic center of Orange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRemainsIn Context triple: [Colonia Julia Firma Secundanorum Arausio, hasRemainsIn, historic center of Orange]
-
A.
hasRemainsOf
chosen
Indicates that one entity physically contains, preserves, or is associated with the leftover physical traces or remnants of another entity.
-
B.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
C.
visibleRemains
Indicates that some physical remnants of an entity or event can still be seen or visually detected.
-
D.
hasEnd
Indicates that one entity serves as the terminal point, boundary, or conclusion of another entity or process.
-
E.
hasCurrent
Indicates that an entity presently possesses, exhibits, or is associated with a particular state, attribute, or resource at the current time.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58e153908190ac8f578e03aecdfc |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5228b70c8190ac48705e35a710c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.