Triple
T10390463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Croton Aqueduct Trail |
E244878
|
entity |
| Predicate | isBasedOnInfrastructureFrom |
P7125
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Old Croton Aqueduct Trail, isBasedOnInfrastructureFrom, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBasedOnInfrastructureFrom Context triple: [Old Croton Aqueduct Trail, isBasedOnInfrastructureFrom, 19th century]
-
A.
isBasedOn
chosen
Indicates that one entity is derived from, inspired by, or developed using the content, structure, or principles of another entity.
-
B.
isPartOfInfrastructure
Indicates that something belongs to, is included within, or functions as a component of a larger infrastructure system.
-
C.
usesInfrastructure
Indicates that one entity makes use of, depends on, or operates through the infrastructure provided or managed by another entity.
-
D.
areBasedOn
Indicates that one entity is founded, derived, or developed from the principles, content, or structure of another entity.
-
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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9b4f7d08190bcb16d3b4c8f22ad |
completed | April 7, 2026, 11:25 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb0e7a88190bec0b7a52c70dfe2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 12:05 p.m.