Triple
T1935474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spotlight search |
E41433
|
entity |
| Predicate | canExclude |
P3119
|
FINISHED |
| Object | specific folders from indexing |
—
|
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: specific folders from indexing | Statement: [Spotlight search, canExclude, specific folders from indexing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canExclude Context triple: [Spotlight search, canExclude, specific folders from indexing]
-
A.
excludes
chosen
Indicates that one entity deliberately omits, leaves out, or does not allow the inclusion of another entity within a set, group, or context.
-
B.
exclusionBasis
Indicates the reason or criterion used to exclude an entity from a set, process, or consideration.
-
C.
acquisitionExcludes
Indicates that a particular acquisition explicitly does not include certain entities, assets, or rights within its scope.
-
D.
excludeRange
Indicates that certain values, items, or elements falling within a specified range are to be omitted or not considered.
-
E.
excludesRegion
Indicates that one entity explicitly omits, leaves out, or does not apply to a specified region or geographic area.
- 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb29c7be08190986df157bf5d7c9e |
completed | March 7, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69abaff07cf88190b4883c5f17f90abd |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.