Triple
T24976507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raleigh Grifter |
E625036
|
entity |
| Predicate | intendedRider |
P12077
|
FINISHED |
| Object | children |
—
|
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: children | Statement: [Raleigh Grifter, intendedRider, children]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedRider Context triple: [Raleigh Grifter, intendedRider, children]
-
A.
intendedRiderExperience
Indicates the type or quality of experience that is planned or designed for a rider in the context of a ride or transportation service.
-
B.
riderType
Indicates the category or role of a rider in relation to a ride, transport service, or vehicle (e.g., passenger, driver, courier).
-
C.
hasOwnerRider
Indicates that an entity (such as an animal or vehicle) has a specific person who both owns it and rides or uses it.
-
D.
primaryRiders
chosen
Indicates that the referenced entities are the main or principal riders associated with a particular vehicle, trip, or ride-related event.
-
E.
managedRider
Indicates that one entity was responsible for directing, organizing, or overseeing the activities or career of a rider.
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 18, 2026, 6:02 a.m.