Triple
T8192999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ola Share |
E191358
|
entity |
| Predicate | matchingCriterion |
P10212
|
FINISHED |
| Object | similar route |
—
|
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: similar route | Statement: [Ola Share, matchingCriterion, similar route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchingCriterion Context triple: [Ola Share, matchingCriterion, similar route]
-
A.
matchType
chosen
Indicates the specific category or nature of how two or more entities correspond or align with each other within a given context.
-
B.
compositionCriterion
Indicates the rule or standard by which components are selected, combined, or arranged to form a whole.
-
C.
selectionCriteria
Indicates the conditions or rules used to choose certain entities from a larger set.
-
D.
listingCriterion
Indicates the rule or standard used to determine how items are selected, ordered, or displayed in a listing.
-
E.
matchTypes
Indicates that two or more entities share the same type or category according to a specified classification.
- 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_69ca82c5b6948190a583c096fb0a6c71 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb5c1d7aa48190adbbce88b3bed1a3 |
completed | March 31, 2026, 5:31 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:42 p.m.