Triple
T528532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AOL Instant Messenger |
E10976
|
entity |
| Predicate | typicalUserBase |
P7221
|
FINISHED |
| Object | mainstream internet users |
—
|
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: mainstream internet users | Statement: [AOL Instant Messenger, typicalUserBase, mainstream internet users]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalUserBase Context triple: [AOL Instant Messenger, typicalUserBase, mainstream internet users]
-
A.
userBase
chosen
Indicates that one entity serves as the primary or foundational group of users associated with another entity.
-
B.
typicalAudience
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
C.
mainBase
Indicates that one entity serves as the primary or central base or headquarters for another entity.
-
D.
socialBase
Indicates a foundational social relationship or structure that underlies or supports interactions between entities.
-
E.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1d39b4c81909f265b3501b5ec1d |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f01ac3ec8190a94a05955532c7fa |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.