Triple
T13856166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chevaleret |
E333068
|
entity |
| Predicate | hasValidationSystem |
P23074
|
FINISHED |
| Object | turnstiles |
—
|
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: turnstiles | Statement: [Chevaleret, hasValidationSystem, turnstiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasValidationSystem Context triple: [Chevaleret, hasValidationSystem, turnstiles]
-
A.
supportsValidationOf
chosen
Indicates that one entity provides the mechanisms or conditions necessary for another entity to be checked or verified for correctness or compliance.
-
B.
hasAccountabilitySystem
Indicates that an entity has a defined mechanism or structure in place for assigning, tracking, and enforcing responsibility for actions or outcomes.
-
C.
hasPASystem
Indicates that an entity possesses or is equipped with a public address (PA) system.
-
D.
hasDisciplineSystem
Indicates that an entity possesses or is governed by a particular system of rules, methods, or practices for maintaining discipline.
-
E.
hasValidity
Indicates that something possesses a period or condition during which it is considered legally, logically, or functionally acceptable or in force.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02dc9f488190b7181dcb7e304632 |
completed | April 14, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:14 p.m.