Triple
T662974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pony Express |
E11796
|
entity |
| Predicate | riderRequirements |
P1130
|
FINISHED |
| Object | lightweight |
—
|
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: lightweight | Statement: [Pony Express, riderRequirements, lightweight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riderRequirements Context triple: [Pony Express, riderRequirements, lightweight]
-
A.
supportsRiderCategory
Indicates that one entity is capable of accommodating, enabling, or being compatible with a specified rider category.
-
B.
ridingSpecialty
Indicates that one entity has a particular area of expertise or focus related to riding (e.g., a specific riding style, discipline, or type).
-
C.
primaryRiders
Indicates that the referenced entities are the main or principal riders associated with a particular vehicle, trip, or ride-related event.
-
D.
eligibilityCriteria
chosen
Indicates the conditions or requirements that must be satisfied for an entity to qualify for or be considered eligible for something.
-
E.
visitorRequirement
Indicates the conditions or criteria that must be met by a visitor in order to be allowed or accepted.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49fd081e8819097f289961f5eff29 |
completed | March 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69a49d153a948190b3ccdc331ed33617 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.