Triple
T28264004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google+ |
E712652
|
entity |
| Predicate | enterpriseVersionContinuation |
P165433
|
FINISHED |
| Object | Google+ for G Suite |
—
|
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+ for G Suite | Statement: [Google+, enterpriseVersionContinuation, Google+ for G Suite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enterpriseVersionContinuation Context triple: [Google+, enterpriseVersionContinuation, Google+ for G Suite]
-
A.
continuousVersionName
Indicates that one entity is the name or label assigned to a continuous or ongoing version of another entity.
-
B.
hasContinuousVersion
Indicates that one entity is a continuous or uninterrupted form, edition, or variant of another entity.
-
C.
versionExample
Indicates that one entity serves as an example or illustrative instance of a particular version of another entity.
-
D.
laterVersion
Indicates that one entity is a subsequent or more recent version of another entity in a version sequence.
-
E.
laterVersionsCapability
Indicates that one entity has the capability to support, handle, or be compatible with later versions of another 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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f659355a208190be2609ffc7a9c427 |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 27, 2026, 11:13 p.m.