Triple
T28828609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neptune |
E727980
|
entity |
| Predicate | notableBuildNumber |
P203503
|
FINISHED |
| Object | 5111 |
—
|
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: 5111 | Statement: [Neptune, notableBuildNumber, 5111]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBuildNumber Context triple: [Neptune, notableBuildNumber, 5111]
-
A.
notableVersionType
Indicates that one version of an entity is recognized as particularly significant or noteworthy relative to other versions.
-
B.
buildNumberBase
Indicates constructing or establishing a numerical base or foundational number system upon which other values or calculations are defined.
-
C.
hasNotableVersion
Indicates that an entity has a specific version or variant that is particularly significant, distinguished, or noteworthy compared to other versions.
-
D.
notableRelease
Indicates that an entity is a significant or prominent release (such as a major version, edition, or launch) associated with another entity.
-
E.
notableBranch
Indicates that one entity is a particularly significant or prominent subdivision, offshoot, or branch of another entity.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_6a01926e2f348190a632eff5c91db5e0 |
completed | May 11, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_6a01923488f4819094d79a27f4bc8ab8 |
completed | May 11, 2026, 8:24 a.m. |
| PDg | Predicate description generation | batch_6a01926d10988190b6fbf03866337860 |
completed | May 11, 2026, 8:25 a.m. |
Created at: April 28, 2026, 6:37 a.m.