Triple
T36937510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IW 2.0 |
E913657
|
entity |
| Predicate | hasRelationshipToEarlierVersion |
P205651
|
FINISHED |
| Object | enhanced functionality |
—
|
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: enhanced functionality | Statement: [IW 2.0, hasRelationshipToEarlierVersion, enhanced functionality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelationshipToEarlierVersion Context triple: [IW 2.0, hasRelationshipToEarlierVersion, enhanced functionality]
-
A.
hasEarlierVersion
Indicates that one entity is an earlier or prior version of another entity in a version sequence.
-
B.
isVersionOf
Indicates that one entity is a particular version, edition, or variant derived from another entity.
-
C.
isYoungerVersionOf
Indicates that one entity represents the same individual as another entity, but at an earlier, younger stage in their life.
-
D.
earlierVersionsCapability
Indicates that an entity has the ability to access, handle, or interact with earlier versions of another entity or resource.
-
E.
previousVersionIncluded
Indicates that an earlier version of an entity was contained within, or formed part of, the current 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_69f76e8a6a5c81909c1febf32bf3fe23 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:13 p.m.