Triple
T6476654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clock Court |
E146088
|
entity |
| Predicate | positionOfClock |
P3250
|
FINISHED |
| Object | over gateway on north side |
—
|
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: over gateway on north side | Statement: [Clock Court, positionOfClock, over gateway on north side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOfClock Context triple: [Clock Court, positionOfClock, over gateway on north side]
-
A.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
B.
clockType
Indicates the type or category of a clock associated with an entity (e.g., analog, digital, system clock, etc.).
-
C.
positionInRosary
Indicates the specific sequential place an element occupies within the ordered structure of a rosary.
-
D.
positionOn
chosen
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
E.
instrumentClusterPosition
Indicates the spatial location or mounting position of an instrument cluster relative to a reference point in a system or vehicle.
- 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_69c008fec7408190af7b146dc63d9750 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a49b3bc8190ad80c6ca2dd15c68 |
completed | March 22, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69c0673f6d48819080e10c85155c7195 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:51 p.m.