Triple
T35547788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryan Preece |
E1027265
|
entity |
| Predicate | hasCarManufacturerExperience |
P136773
|
FINISHED |
| Object | Chevrolet |
—
|
NE NERFINISHED |
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: Chevrolet | Statement: [Ryan Preece, hasCarManufacturerExperience, Chevrolet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCarManufacturerExperience Context triple: [Ryan Preece, hasCarManufacturerExperience, Chevrolet]
-
A.
hasExperienceOf
Indicates that one entity has undergone, encountered, or lived through a particular event, situation, or activity associated with another entity.
-
B.
hasPastExperience
chosen
Indicates that an entity has previously engaged in or undergone the specified activity, role, or situation in the past.
-
C.
hasExperienceCharacteristic
Indicates that an entity possesses a particular quality, feature, or attribute related to its experience.
-
D.
hasExperienceElement
Indicates that an experience is composed of, or includes, a specific constituent element or component.
-
E.
drivingExperience
Indicates the extent or history of a person's involvement in driving vehicles, typically measured by duration, frequency, or level of skill.
- 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_69f76e008ba08190927acd8e5e0344c8 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff97637ad881908c24fe2cc6b036db |
completed | May 9, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69ff96c43a808190942eeda1934602db |
completed | May 9, 2026, 8:19 p.m. |
Created at: May 3, 2026, 4:04 p.m.