Triple
T14447980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brave Talk |
E358255
|
entity |
| Predicate | requiresAdditionalApp |
P11910
|
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, requiresAdditionalApp, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresAdditionalApp Context triple: [Brave Talk, requiresAdditionalApp, no]
-
A.
requiresApplicationTo
Indicates that one entity can only access, use, or obtain another entity if a formal application or request process is completed.
-
B.
requiresApplicationOf
Indicates that performing one entity or process depends on actively applying or using another entity, method, or resource.
-
C.
requiresInstallation
Indicates that one entity must be installed or set up before the other can be used or become operational.
-
D.
requiresDevice
Indicates that performing the specified action or relationship is contingent on the presence or use of a particular device.
-
E.
requiresSoftware
chosen
Indicates that one entity depends on specific software being present or installed in order to function, operate, or be used.
- 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_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. |
Created at: April 10, 2026, 1:19 a.m.