Triple
T14447991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brave Talk |
E358255
|
entity |
| Predicate | storesCallMetadataByDefault |
P114318
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Brave Talk, storesCallMetadataByDefault, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storesCallMetadataByDefault Context triple: [Brave Talk, storesCallMetadataByDefault, no]
-
A.
dynamicMetadataSupport
Indicates that the subject system or component is capable of handling metadata that can change or be updated at runtime rather than being fixed or static.
-
B.
callsTo
Indicates that one entity initiates a call or communication action directed toward another entity.
-
C.
nowCalled
Indicates that an entity previously known by one name is currently referred to by a different name.
-
D.
hasCallInNumber
Indicates that an entity has an associated telephone number designated for receiving incoming calls.
-
E.
callsFor
Indicates that one entity requires, demands, or requests the occurrence of another action, condition, or entity.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9160126c8190a2862a1a3dde1aff |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:19 a.m.