Triple
T22476350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charonne |
E555638
|
entity |
| Predicate | hasValidationGates |
P4365
|
FINISHED |
| Object | automatic fare gates |
—
|
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: automatic fare gates | Statement: [Charonne, hasValidationGates, automatic fare gates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasValidationGates Context triple: [Charonne, hasValidationGates, automatic fare gates]
-
A.
hasGatesFor
Indicates that one entity is equipped with or provides access through one or more gates intended for another entity.
-
B.
hasGate
chosen
Indicates that one entity possesses, includes, or is equipped with a gate as part of its structure or configuration.
-
C.
hasGatekeeper
Indicates that one entity serves as a controlling or mediating gatekeeper for access to another entity.
-
D.
hasGateRange
Indicates the range of values or interval within which a gate or gating parameter is valid or operates.
-
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_69e11e52c2048190952dc5df209b9bed |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15be48cec8190baff90f8566a85d0 |
completed | April 29, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.