Triple
T28375408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luigi's Rollickin' Roadsters |
E718742
|
entity |
| Predicate | transferAccessible |
P157700
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Luigi's Rollickin' Roadsters, transferAccessible, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferAccessible Context triple: [Luigi's Rollickin' Roadsters, transferAccessible, yes]
-
A.
accessibleTransfer
chosen
Indicates that a transfer between entities can be performed in a way that is usable and reachable by people with accessibility needs.
-
B.
transferFeature
Indicates a relationship where a feature, attribute, or capability is moved or reassigned from one entity to another.
-
C.
transferBetween
Indicates a movement or handover of something from one entity to another, typically changing its location, ownership, or control between them.
-
D.
transferable
Indicates that a right, property, or obligation can be legally or practically passed from one entity to another.
-
E.
transferType
Indicates the specific method or category of how something is transferred from one entity to another.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: April 28, 2026, 1:02 a.m.