Triple
T28195934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | inDriver |
E716446
|
entity |
| Predicate | appCategory |
P162628
|
FINISHED |
| Object | travel |
—
|
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: travel | Statement: [inDriver, appCategory, travel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appCategory Context triple: [inDriver, appCategory, travel]
-
A.
notableAppCategory
Indicates that an application is recognized as significant or prominent within a particular category or classification of apps.
-
B.
applicationTool
Indicates that one entity is a tool or instrument used to apply, operate, or carry out the function of another entity.
-
C.
softwareCategoryFocus
chosen
Indicates that something is primarily concerned with, or directed toward, a particular category or type of software.
-
D.
apparentCategory
Indicates the category or type that something seems to belong to based on its observable characteristics, regardless of its true or underlying classification.
-
E.
applicationRange
Indicates the scope or extent within which something (such as a rule, function, or process) is validly applied or operates.
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f642d17c688190838ecd2f002afc89 |
completed | May 2, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:28 p.m.