Triple
T13325719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman aqueduct |
E317436
|
entity |
| Predicate | designedToSupply |
P17063
|
FINISHED |
| Object | cities |
—
|
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: cities | Statement: [Roman aqueduct, designedToSupply, cities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToSupply Context triple: [Roman aqueduct, designedToSupply, cities]
-
A.
suppliesTo
chosen
Indicates that one entity provides or delivers goods, services, or resources to another entity.
-
B.
supplyType
Indicates the kind or category of supply associated with or provided in a given relationship or context.
-
C.
suppliesPowerTo
Indicates that one entity provides electrical or energy power required for the operation or functioning of another entity.
-
D.
designedToSupplement
Indicates that one entity is created or intended to enhance, complete, or add to the function, content, or effect of another entity.
-
E.
suppliedAs
Indicates that one entity is provided, delivered, or made available in the form, role, or capacity of 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6babd88190a5d529df9584b9a4 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:30 p.m.