Triple
T2660823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Distribution Capability |
E54720
|
entity |
| Predicate | hasVersioning |
P28478
|
FINISHED |
| Object | multiple schema versions released over time |
—
|
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: multiple schema versions released over time | Statement: [New Distribution Capability, hasVersioning, multiple schema versions released over time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVersioning Context triple: [New Distribution Capability, hasVersioning, multiple schema versions released over time]
-
A.
hasVersionCount
Indicates the total number of distinct versions associated with a given entity.
-
B.
hasVersionNumber
Indicates that an entity is associated with a specific version identifier or number.
-
C.
hasVersionManager
Indicates that one entity is responsible for managing, controlling, or overseeing the versions or revisions of another entity.
-
D.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
E.
hasMultipleVersions
chosen
Indicates that an entity exists in more than one distinct version or revision.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd9504d10819091abc03532a2fa6d |
completed | March 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.