Triple
T15226827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barbara Ann |
E363897
|
entity |
| Predicate | hasEnduringPresenceIn |
P11111
|
FINISHED |
| Object | popular culture |
—
|
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: popular culture | Statement: [Barbara Ann, hasEnduringPresenceIn, popular culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnduringPresenceIn Context triple: [Barbara Ann, hasEnduringPresenceIn, popular culture]
-
A.
hasHumanPresence
Indicates that humans are physically present in or occupying a given location, object, or context.
-
B.
hasLargePresenceIn
chosen
Indicates that an entity maintains a significant or dominant level of activity, influence, or representation within a specified location, domain, or context.
-
C.
traditionalPresenceIn
Indicates that an entity has a customary or historically established presence within a particular place, context, or setting.
-
D.
confirmedPresenceOf
Indicates that the presence or existence of an entity has been verified as true or established with certainty.
-
E.
hasPlaceIn
Indicates that one entity occupies, is located within, or holds a specific position in another entity or context.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0078bb32881909927561c6c072546 |
completed | April 15, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69deca8479188190b2e5d3bc708d7d07 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:12 a.m.