Triple
T32481037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Live Edition |
E830108
|
entity |
| Predicate | installationOptional |
P174491
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Live Edition, installationOptional, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: installationOptional Context triple: [Live Edition, installationOptional, yes]
-
A.
installationFeature
Indicates that one entity serves as a feature, component, or functional element of another entity’s installation.
-
B.
installationVariable
Indicates that a variable is associated with, defined for, or used during an installation process or configuration.
-
C.
installationCommand
Indicates the command or set of commands used to install a particular software, package, or component.
-
D.
requiresInstallation
Indicates that one entity must be installed or set up before the other can be used or become operational.
-
E.
installationForm
Indicates the specific method, configuration, or format in which something is installed or set up.
- 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_69f3491ff3b48190b50a7fa00bb05b1f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c395640c81908808b2d4d40f26e7 |
completed | May 3, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 12:58 a.m.