Triple
T9569474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gate of Charisius |
E230876
|
entity |
| Predicate | approachedBy |
P31133
|
FINISHED |
| Object | road from Adrianople |
—
|
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: road from Adrianople | Statement: [Gate of Charisius, approachedBy, road from Adrianople]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approachedBy Context triple: [Gate of Charisius, approachedBy, road from Adrianople]
-
A.
attendedBy
Indicates that an event, place, or activity is participated in or visited by a particular person or group.
-
B.
askedAboutBy
Indicates that one entity is the subject of a question or inquiry made by another entity.
-
C.
approachDirection
chosen
Indicates the direction or bearing from which one entity moves closer to or advances toward another entity.
-
D.
addressedBy
Indicates that something (such as an issue, request, or item) is handled, dealt with, or responded to by a particular agent or entity.
-
E.
engagedBy
Indicates that an entity is actively involved, occupied, or participating in an activity, process, or interaction initiated or provided by another entity.
- 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_69ca847f22188190a56e4a97625bef22 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd998940c881909f9025512cf72fe9 |
completed | April 1, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69ccd59b960c8190966a8870a2426bd5 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:04 p.m.