Triple
T11606593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MBTA CharlieTicket |
E275274
|
entity |
| Predicate | validatedAt |
P100568
|
FINISHED |
| Object | subway 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: subway fare gates | Statement: [MBTA CharlieTicket, validatedAt, subway fare gates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: validatedAt Context triple: [MBTA CharlieTicket, validatedAt, subway fare gates]
-
A.
timeOfAttestation
Indicates the specific time at which a statement, document, or claim is formally attested or verified.
-
B.
securedDate
Indicates the date on which something was formally obtained, locked in, or guaranteed (e.g., a deal, reservation, or right).
-
C.
formedAt
Indicates the time or date at which an entity was created, established, or came into existence.
-
D.
hasValidityPeriod
Indicates that something is associated with a specific time span during which it is considered valid or in effect.
-
E.
validityType
Indicates the specific kind or category of validity that characterizes how or under what conditions something is considered valid.
- F. None of above. chosen
Provenance (4 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d89551649c81908096ff392677442d |
completed | April 10, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_69d85dd20d188190863d1190d4c16048 |
completed | April 10, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69d87f2e67108190ac36bf47aac12fa8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:38 p.m.