Triple
T21544614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Seu |
E531588
|
entity |
| Predicate | mainOrientation |
P135190
|
FINISHED |
| Object | towards the sea |
—
|
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: towards the sea | Statement: [La Seu, mainOrientation, towards the sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainOrientation Context triple: [La Seu, mainOrientation, towards the sea]
-
A.
currentOrientation
Indicates the present directional alignment or facing angle of an entity relative to a reference frame or coordinate system.
-
B.
orientationType
Indicates the specific kind or category of orientation relationship that exists between entities (such as spatial, directional, or alignment-based orientation).
-
C.
sessionOrientation
Indicates the directional or spatial alignment relationship established between entities within a session or interaction context.
-
D.
functionalOrientation
Indicates a relationship where an entity is characterized by the specific function, role, or operational purpose it is oriented or designed to fulfill.
-
E.
locationOrientation
chosen
Indicates how one entity is spatially oriented or positioned relative to a specific location or reference point.
- 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_69e0c45f17148190949c330ab9c27706 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeb58e38808190888f3501cf4fff7c |
completed | April 27, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:28 p.m.