Triple
T28264007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google+ |
E712652
|
entity |
| Predicate | userBasePeakEstimate |
P92341
|
FINISHED |
| Object | hundreds of millions of registered profiles |
—
|
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: hundreds of millions of registered profiles | Statement: [Google+, userBasePeakEstimate, hundreds of millions of registered profiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: userBasePeakEstimate Context triple: [Google+, userBasePeakEstimate, hundreds of millions of registered profiles]
-
A.
approximateUserPeak
chosen
Indicates that one value or event is an estimated or inferred maximum point associated with a particular user.
-
B.
userCount
Indicates the number of users associated with or involved in a given context or entity.
-
C.
estimatedMemberCount
Indicates the approximate or predicted number of members associated with an entity.
-
D.
userPopulation
Indicates the total number of users associated with or served by a given system, service, or context.
-
E.
usagePeak
Indicates that the usage or consumption of something reaches its highest level or intensity during a particular time or condition.
- 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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6441c2ed081909128d8fe21b14fa4 |
completed | May 2, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:13 p.m.