Triple
T14538594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Java 1.3 |
E341113
|
entity |
| Predicate | minorVersionNumber |
P114847
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Java 1.3, minorVersionNumber, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minorVersionNumber Context triple: [Java 1.3, minorVersionNumber, 3]
-
A.
majorVersion
Indicates that one entity specifies or corresponds to the primary (major) version number of another entity in a versioning scheme.
-
B.
latestMinorVersion
Indicates that one version is the most recent minor (non-major) update within the series of versions derived from another version.
-
C.
majorRevision
Indicates a substantial change or overhaul made to something, significantly altering its previous form or content.
-
D.
principalVersionFor
Indicates a relationship where one version of an entity is designated as the primary or authoritative version for another related entity.
-
E.
laterVersion
Indicates that one entity is a subsequent or more recent version of another entity in a version sequence.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb1bb90008190947ac0961393446d |
completed | April 14, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69de5c546c7081909e27d504ec360c5c |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de610330a48190b558235a14c0dc9f |
completed | April 14, 2026, 3:45 p.m. |
Created at: April 10, 2026, 1:22 a.m.