Triple
T3252814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Road (Große Straße) |
E68220
|
entity |
| Predicate | hasFunctionInComplex |
P46874
|
FINISHED |
| Object | main processional route |
—
|
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: main processional route | Statement: [Great Road (Große Straße), hasFunctionInComplex, main processional route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFunctionInComplex Context triple: [Great Road (Große Straße), hasFunctionInComplex, main processional route]
-
A.
hasFunctionInPlot
Indicates that an entity serves a particular role or purpose within the structure or progression of a plot.
-
B.
hasComplex
Indicates that one entity possesses, is associated with, or is part of a larger composite structure or complex formed with another entity.
-
C.
usesFunction
Indicates that one entity employs, invokes, or relies on a particular function to perform an operation or achieve a result.
-
D.
hasFunctionInScore
Indicates that an entity serves a specific functional role within a musical score.
-
E.
hasHubFunction
Indicates that an entity serves as a central hub or coordinating point for certain activities, connections, or functions within a system.
- F. None of above. chosen
Provenance (4 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_69ad858f74408190bcbd07f967cd7bd0 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf440bb88190a2450405afae7f1f |
completed | March 8, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69ada41ae74081909a0d1d696be8e35e |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada525bb2c8190b773efe6d696b6ab |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:09 p.m.