Triple
T10096224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Socialcam |
E215873
|
entity |
| Predicate | userBaseCharacteristic |
P7221
|
FINISHED |
| Object | rapid early growth |
—
|
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: rapid early growth | Statement: [Socialcam, userBaseCharacteristic, rapid early growth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: userBaseCharacteristic Context triple: [Socialcam, userBaseCharacteristic, rapid early growth]
-
A.
userProfileFeatures
Indicates that certain characteristics, settings, or attributes are associated with and define a user's profile.
-
B.
userBase
chosen
Indicates that one entity serves as the primary or foundational group of users associated with another entity.
-
C.
commonAttribute
Indicates that two or more entities share the same specified attribute or property.
-
D.
groupCharacterization
Indicates how a group as a whole is described or characterized in terms of its shared properties, traits, or defining features.
-
E.
demographicsCharacteristic
Indicates that one entity serves as a demographic attribute or characteristic (such as age, gender, ethnicity, etc.) that describes or classifies another entity.
- 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_69ca83a4947c8190823a7495dc5d96ed |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd0798c248190af675e30e280daa8 |
completed | April 2, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9b853c8190a2af993ce9b21309 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:02 p.m.