Triple
T22904801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seven Pilgrim Churches of Rome |
E568415
|
entity |
| Predicate | hasRouteForm |
P169
|
FINISHED |
| Object | circular itinerary |
—
|
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: circular itinerary | Statement: [Seven Pilgrim Churches of Rome, hasRouteForm, circular itinerary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRouteForm Context triple: [Seven Pilgrim Churches of Rome, hasRouteForm, circular itinerary]
-
A.
hasRoute
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
-
B.
hasForm
chosen
Indicates that one entity possesses, exhibits, or is characterized by a particular shape, structure, or configuration.
-
C.
hasFormFor
Indicates that one entity possesses or provides a specific form or document intended to be used by another entity or for a particular purpose.
-
D.
hasRouteType
Indicates that there is a specific kind or category of route associated with an entity (e.g., road, rail, bus line).
-
E.
hasRouteConsideration
Indicates that one entity takes another entity into account when planning, evaluating, or determining a route.
- 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_69e2458cd9e48190943ad2e34485d939 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f180198fe88190b2f8c2a827d95fdc |
completed | April 29, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:41 p.m.