Triple
T19762453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carfax, Oxford |
E474662
|
entity |
| Predicate | isOrientationPointFor |
P11053
|
FINISHED |
| Object | visitors to Oxford |
—
|
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: visitors to Oxford | Statement: [Carfax, Oxford, isOrientationPointFor, visitors to Oxford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOrientationPointFor Context triple: [Carfax, Oxford, isOrientationPointFor, visitors to Oxford]
-
A.
hasOrientation
Indicates that one entity is positioned or directed in a specific spatial or conceptual alignment relative to a reference frame or another entity.
-
B.
isReferencePointFor
chosen
Indicates that one entity serves as a positional or conceptual basis used to locate, measure, or interpret another entity.
-
C.
isPointWhere
Indicates that one entity is the specific location or point at which another entity, event, or condition occurs or is defined.
-
D.
isOnAxis
Indicates that one entity lies directly along a specified axis or reference line defined by another entity or coordinate system.
-
E.
hasRegionalOrientation
Indicates that an entity is oriented toward, focused on, or primarily associated with a specific geographic region.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65320df3c8190b34f9908d5da48d9 |
completed | April 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.