Triple
T24933790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metcard |
E623257
|
entity |
| Predicate | allowedTransferBetween |
P28517
|
FINISHED |
| Object | train and bus |
—
|
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: train and bus | Statement: [Metcard, allowedTransferBetween, train and bus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowedTransferBetween Context triple: [Metcard, allowedTransferBetween, train and bus]
-
A.
allowsTransferTo
Indicates that one entity permits or enables the transfer of something (such as rights, funds, or data) to another specified entity.
-
B.
accessibleTransfer
Indicates that a transfer between entities can be performed in a way that is usable and reachable by people with accessibility needs.
-
C.
allowedTransport
chosen
Indicates that a particular mode or means of transport is permitted for use between the related entities.
-
D.
transferBetween
Indicates a movement or handover of something from one entity to another, typically changing its location, ownership, or control between them.
-
E.
allowsTransferOfFunctionsFrom
Indicates that one entity grants permission or enables the shifting of responsibilities, duties, or operational functions from itself to 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_69e2fac6b5a48190a1c38857f00915a9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 18, 2026, 5:30 a.m.