Triple
T1935172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gatekeeper |
E41427
|
entity |
| Predicate | blocks |
P19715
|
FINISHED |
| Object | apps from unidentified developers by default |
—
|
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: apps from unidentified developers by default | Statement: [Gatekeeper, blocks, apps from unidentified developers by default]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blocks Context triple: [Gatekeeper, blocks, apps from unidentified developers by default]
-
A.
block
chosen
Indicates preventing or obstructing another entity’s action, movement, or access.
-
B.
relatedBlock
Indicates that one block is associated with or connected to another block in some relevant way.
-
C.
statBlocks
Indicates that one entity provides or contains statistical blocks or structured stat information about another entity.
-
D.
buildingSection
Indicates a relationship where one entity is a specific section, part, or subdivision of a larger building.
-
E.
bridges
Indicates that one entity connects or links two or more other entities, allowing passage, transition, or interaction between them.
- 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.