Triple
T24054523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pepsi Max Lemon |
E595757
|
entity |
| Predicate | hasGlobalOwner |
P154686
|
FINISHED |
| Object | PepsiCo |
—
|
NE NERFINISHED |
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: PepsiCo | Statement: [Pepsi Max Lemon, hasGlobalOwner, PepsiCo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGlobalOwner Context triple: [Pepsi Max Lemon, hasGlobalOwner, PepsiCo]
-
A.
hasGlobalHost
Indicates that an entity is associated with or served by a host that is accessible or applicable at a global (system-wide or worldwide) level.
-
B.
hasGlobalRole
Indicates that an entity holds a role or permission set that applies across an entire system or domain, rather than being limited to a specific scope or context.
-
C.
hasGlobalIdentity
Indicates that an entity possesses a unique, overarching identity that is recognized or valid across multiple systems, contexts, or domains.
-
D.
hasOwnerStructure
Indicates that an entity is associated with, or governed by, a particular ownership structure or ownership arrangement.
-
E.
hasOwnerOperator
Indicates that an entity is owned and operated by a specified party, combining both ownership and operational responsibility in a single relationship.
- 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_69e288c184b081909f1f1751fb8e299a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d9d551288190a2b3b6c8c4f3c1b5 |
completed | April 29, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 10:21 p.m.