Triple
T28264008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google+ |
E712652
|
entity |
| Predicate | activeUsersRelativeToCompetitors |
P173377
|
FINISHED |
| Object | significantly lower than Facebook |
—
|
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: significantly lower than Facebook | Statement: [Google+, activeUsersRelativeToCompetitors, significantly lower than Facebook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeUsersRelativeToCompetitors Context triple: [Google+, activeUsersRelativeToCompetitors, significantly lower than Facebook]
-
A.
competitorCount
Indicates the number of competitors associated with a given entity or context.
-
B.
userCount
Indicates the number of users associated with or involved in a given context or entity.
-
C.
screenTimeRelativeToOthers
Indicates how an entity’s amount of screen time compares to that of other entities.
-
D.
competitiveStatus
Indicates the nature or level of competition that exists between entities, such as whether they are rivals, collaborators, or non-competitors.
-
E.
otherUsers
Indicates a relationship where one or more users are distinguished as being different from a given primary or reference user.
- 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_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: April 27, 2026, 11:13 p.m.