Triple
T33324731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AAA Approved Auto Repair |
E853232
|
entity |
| Predicate | allowsSearchBy |
P106401
|
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: [AAA Approved Auto Repair, allowsSearchBy, location]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsSearchBy Context triple: [AAA Approved Auto Repair, allowsSearchBy, location]
-
A.
isSearchable
Indicates that the referenced entity can be discovered or retrieved through a search operation or query.
-
B.
searchesOver
Indicates that one entity actively looks through, queries, or examines another entity or set of entities to find information or items.
-
C.
usedToSearchFor
Indicates that one entity serves as a tool, method, or resource employed to look for, locate, or retrieve another entity.
-
D.
searchingFor
Indicates that one entity is actively seeking, looking for, or attempting to locate another entity.
-
E.
hasSearchField
chosen
Indicates that an entity includes or is associated with a search input field that can be used to query or filter information.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 1, 2026, 1:33 a.m.