Triple
T955999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | App Store |
E20626
|
entity |
| Predicate | searchFeature |
P21822
|
FINISHED |
| Object | keyword search |
—
|
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: keyword search | Statement: [App Store, searchFeature, keyword search]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: searchFeature Context triple: [App Store, searchFeature, keyword search]
-
A.
featureType
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
-
B.
featuresLocation
Indicates that something is characterized by or includes a specific location as one of its notable attributes.
-
C.
featureOfInterest
Indicates the entity or object that is the primary subject or focus of the described observation, measurement, or analysis.
-
D.
formsFeature
Indicates that one entity constitutes or creates a characteristic, component, or distinguishing element of another entity.
-
E.
findingOnFacilities
Indicates a relationship where an inspection or assessment identifies a specific issue, observation, or result associated with particular facilities.
- F. None of above. chosen
Provenance (4 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_69a493b21f2881908132dcf45dcd2f36 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3f981bc819098125554eeeb6375 |
completed | March 1, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a18ecc8190883f6206fe3b0fb6 |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b326d9d88190913c1a892a795707 |
completed | March 1, 2026, 9:44 p.m. |
Created at: March 1, 2026, 7:40 p.m.