Triple
T1634436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google Docs |
E35329
|
entity |
| Predicate | supportsVersionHistory |
P21515
|
FINISHED |
| Object | named versions |
—
|
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: named versions | Statement: [Google Docs, supportsVersionHistory, named versions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsVersionHistory Context triple: [Google Docs, supportsVersionHistory, named versions]
-
A.
includesChangeHistory
chosen
Indicates that the subject maintains or contains a record of past modifications or changes made to it.
-
B.
hasMultipleVersions
Indicates that an entity exists in more than one distinct version or revision.
-
C.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
D.
hasVersionCount
Indicates the total number of distinct versions associated with a given entity.
-
E.
upgradeHistory
Indicates the record of changes where one version, state, or configuration has been replaced or improved by another over time.
- 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_69a886036bc081909ff5de16dbe5e8ea |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907cac610819083cafd4396b6d66c |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.