Triple
T14269406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ager Gallicus |
E353738
|
entity |
| Predicate | laterOrganizedAs |
P1504
|
FINISHED |
| Object | Roman colony |
—
|
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: Roman colony | Statement: [Ager Gallicus, laterOrganizedAs, Roman colony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterOrganizedAs Context triple: [Ager Gallicus, laterOrganizedAs, Roman colony]
-
A.
organizedAt
Indicates that an event or activity was arranged, planned, or hosted at a specific location or venue.
-
B.
oftenOrganizedBy
Indicates that an event, activity, or process is frequently arranged, coordinated, or hosted by a particular agent or entity.
-
C.
organisedSince
Indicates that an entity has been formally organized or established starting from a specified point in time.
-
D.
organizedFrom
Indicates that something has been arranged, structured, or formed starting from a specified source or initial set of elements.
-
E.
reorganizedAs
chosen
Indicates that an existing entity has been restructured or reconfigured into a new organizational form or arrangement.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de657fe6708190b41de48c43cff647 |
completed | April 14, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a7d586c8190846ff242bbf5ac53 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:10 a.m.