Triple
T21569135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Pass |
E532238
|
entity |
| Predicate | notValidOn |
P69175
|
FINISHED |
| Object | most urban metro systems |
—
|
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: most urban metro systems | Statement: [Global Pass, notValidOn, most urban metro systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notValidOn Context triple: [Global Pass, notValidOn, most urban metro systems]
-
A.
nonEligibility
Indicates that an entity does not meet the required conditions or criteria to qualify for a specified status, benefit, or action.
-
B.
notAvailableFor
chosen
Indicates that an entity is currently not accessible, usable, or eligible for a particular action, purpose, or association.
-
C.
notEnforcedBy
Indicates that a rule, policy, or obligation is not upheld, imposed, or carried out by the referenced enforcing entity.
-
D.
notEstablishedBy
Indicates that a given entity, state, or condition does not originate from, is not created by, and is not the result of the specified agent or source.
-
E.
notStatus
Indicates that an entity does not have, is not in, or does not match a specified status or state.
- 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9cb9718819094fc95b25df68bd1 |
completed | April 27, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:30 p.m.