Triple
T17721653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adult Opal card |
E442350
|
entity |
| Predicate | supportsOpalBenefits |
P101952
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Adult Opal card, supportsOpalBenefits, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsOpalBenefits Context triple: [Adult Opal card, supportsOpalBenefits, true]
-
A.
benefitsOperator
Indicates that one entity provides an advantage, profit, or positive outcome to an operator entity.
-
B.
hasBenefit
Indicates that one entity provides an advantage, improvement, or positive outcome to another entity.
-
C.
benefitAppliesTo
chosen
Indicates that a particular benefit is applicable to, or valid for, a specified entity or context.
-
D.
benefitAvailableAt
Indicates that a particular benefit can be obtained, accessed, or used at a specified location, time, or context.
-
E.
supportsOperationsIn
Indicates that one entity enables, facilitates, or backs the execution of operations within a specified context, area, or domain of another entity.
- 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47486438c8190abe27eb4eb2c6fdf |
completed | April 19, 2026, 6:21 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:07 a.m.