Triple
T14504069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Gaul |
E340217
|
entity |
| Predicate | sawProcess |
P114487
|
FINISHED |
| Object | Romanization of local populations |
—
|
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: Romanization of local populations | Statement: [Eastern Gaul, sawProcess, Romanization of local populations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sawProcess Context triple: [Eastern Gaul, sawProcess, Romanization of local populations]
-
A.
sawServiceDuring
Indicates that one entity experienced or utilized a service during the time period associated with another entity or event.
-
B.
sawServiceIn
Indicates that an entity observed or experienced a particular service within a specified context, location, or timeframe.
-
C.
sawActionDuring
Indicates that one entity observed an action or event occurring within a specific time period or during another event.
-
D.
sawActionOn
Indicates that one entity visually perceived another entity performing an action.
-
E.
sawServicePeriod
Indicates that one entity observed or was aware of the duration or specific period during which a service was provided or active.
- F. None of above. chosen
Provenance (4 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de94e0f9048190a2d266cfa4f9dfb6 |
completed | April 14, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:21 a.m.