Triple
T28828612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neptune |
E727980
|
entity |
| Predicate | developmentBranch |
P108970
|
FINISHED |
| Object | Windows NT 5.x line |
—
|
NE NERFINISHED |
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: Windows NT 5.x line | Statement: [Neptune, developmentBranch, Windows NT 5.x line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developmentBranch Context triple: [Neptune, developmentBranch, Windows NT 5.x line]
-
A.
developedBranch
Indicates that one branch or offshoot was created, expanded, or evolved from another as its source or origin.
-
B.
developmentVariant
chosen
Indicates that one entity is a variant or alternative form of another in the context of development (e.g., a different developmental version, configuration, or pathway).
-
C.
supportingBranch
Indicates that one branch structurally or functionally supports another branch.
-
D.
branchNumber
Indicates the specific branch identifier or code assigned to distinguish one branch from others within the same organization or system.
-
E.
branchAllocation
Indicates how resources, responsibilities, or items are distributed or assigned across different branches or subdivisions.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 28, 2026, 6:37 a.m.