Triple
T28264006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google+ |
E712652
|
entity |
| Predicate | enterpriseVersionRebrandedAs |
P166211
|
FINISHED |
| Object | Google Currents |
—
|
NE NERFINISHED |
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: Google Currents | Statement: [Google+, enterpriseVersionRebrandedAs, Google Currents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enterpriseVersionRebrandedAs Context triple: [Google+, enterpriseVersionRebrandedAs, Google Currents]
-
A.
enterpriseVersionContinuation
Indicates that one enterprise version is a continuation or successor of another enterprise version in a product or system lifecycle.
-
B.
editionNumberSinceRebranding
Indicates the sequential edition number of something counted from the point in time when it was rebranded, ignoring editions that occurred before the rebranding.
-
C.
versionOf
Indicates that one entity is a specific form, edition, or variant derived from or corresponding to another entity.
-
D.
versionExample
Indicates that one entity serves as an example or illustrative instance of a particular version of another entity.
-
E.
officialVersionSince
Indicates the point in time from which a particular version of something is recognized or treated as the official version.
- 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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 27, 2026, 11:13 p.m.