Triple
T1911964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Becky |
E38129
|
entity |
| Predicate | hasPopularityType |
P25115
|
FINISHED |
| Object | common name |
—
|
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: common name | Statement: [Becky, hasPopularityType, common name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPopularityType Context triple: [Becky, hasPopularityType, common name]
-
A.
popularityType
chosen
Indicates the specific category or nature of how popularity is characterized or measured in the relationship.
-
B.
hasPopularityInfluencedBy
Indicates that the popularity level of one entity is affected or shaped by another specified factor or entity.
-
C.
peakPopularity
Indicates the time or context in which something reaches its highest level of popularity relative to other times or contexts.
-
D.
isPopularWith
Indicates that one entity is well-liked, favored, or widely accepted by another entity or group.
-
E.
hasPopulationType
Indicates that an entity’s population is classified according to a specific type or category (e.g., demographic, biological, or statistical grouping).
- 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_69a8862a26088190aae5243695aeefc0 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafeba3d88190afcce67483d8625b |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.