Triple
T9957760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | October 2018 Update (1809) |
E195486
|
entity |
| Predicate | buildBase |
P42272
|
FINISHED |
| Object | build 17763 |
—
|
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: build 17763 | Statement: [October 2018 Update (1809), buildBase, build 17763]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildBase Context triple: [October 2018 Update (1809), buildBase, build 17763]
-
A.
constructionBase
chosen
Indicates that one entity serves as the foundational structure or base upon which another entity is constructed or built.
-
B.
builder
Indicates that an entity is responsible for constructing, creating, or assembling another entity.
-
C.
buildConfiguration
Indicates the specific setup, options, and parameters used when building or compiling a software project.
-
D.
builtStructureFor
Indicates that one entity constructed or assembled a structure specifically intended for the use, benefit, or purpose of another entity.
-
E.
builtFrom
Indicates that one entity is constructed, composed, or formed using another entity as its material, component, or source.
- 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_69ca82eaaa008190a54fa1a9f954b9ad |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb6cceb608190ad4424afaddcabfa |
completed | April 2, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:46 p.m.