Triple
T30733739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egnatia gens |
E782487
|
entity |
| Predicate | hasNotableInfrastructureAssociation |
P138399
|
FINISHED |
| Object | Via Egnatia |
—
|
NE NERFINISHED |
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: Via Egnatia | Statement: [Egnatia gens, hasNotableInfrastructureAssociation, Via Egnatia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableInfrastructureAssociation Context triple: [Egnatia gens, hasNotableInfrastructureAssociation, Via Egnatia]
-
A.
hasNotableLocationAssociation
Indicates that there is a significant or noteworthy connection between an entity and a specific location.
-
B.
infrastructureAssociatedWith
chosen
Indicates a relationship where a piece of infrastructure is functionally or contextually connected to, supports, or is used by another entity.
-
C.
hasNotableFacility
Indicates that an entity possesses or hosts a facility that is of particular significance, prominence, or interest.
-
D.
hasNotableStructureOn
Indicates that a subject entity possesses or features a significant or noteworthy structure located on it.
-
E.
hasInfrastructureType
Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00532815c881908f10d9594458b3d7 |
completed | May 10, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_6a0052b9f030819081b8105bdcaf6d8f |
completed | May 10, 2026, 9:41 a.m. |
Created at: April 29, 2026, 8:37 p.m.