Triple
T36958857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Build engine |
E914256
|
entity |
| Predicate | sourceCodeStatus |
P98698
|
FINISHED |
| Object | partially released |
—
|
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: partially released | Statement: [Build engine, sourceCodeStatus, partially released]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceCodeStatus Context triple: [Build engine, sourceCodeStatus, partially released]
-
A.
sourceCodeReleased
chosen
Indicates that the source code for a software project or component has been made publicly available or otherwise released for access.
-
B.
sourceStatus
Indicates the current state or condition of a given source within a process, system, or workflow.
-
C.
sourceCodeReleasedBy
Indicates that the source code of a software or project has been made publicly available by a specific releasing entity.
-
D.
sourceCodeLicense
Indicates the legal license under which a piece of source code is distributed or made available.
-
E.
riverCodeStatus
Indicates the current regulatory or classification status assigned to a river under a specific coding or standards system.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:13 p.m.