Triple
T15132005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keyword Planner |
E361442
|
entity |
| Predicate | allowsFilteringBy |
P46801
|
FINISHED |
| Object | location |
—
|
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: location | Statement: [Keyword Planner, allowsFilteringBy, location]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsFilteringBy Context triple: [Keyword Planner, allowsFilteringBy, location]
-
A.
usesFilter
Indicates that one entity applies or employs a filter (such as a criterion, condition, or processing mechanism) to another entity or set of data.
-
B.
hasFilterType
Indicates that an entity is associated with, or constrained by, a specific type or category of filter applied to it.
-
C.
supportsPredicateFiltering
chosen
Indicates that the subject allows or enables filtering operations to be performed based on specific predicates or conditions.
-
D.
isStillAllowedFor
Indicates that one entity continues to have permission or authorization to access, use, or perform something in relation to another entity.
-
E.
allows
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005b194748190801e3956bf2429d4 |
completed | April 15, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69deb9713fe881909dec2fd3f6c84b39 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:06 a.m.