Triple
T32093838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suntory Sungoliath |
E819672
|
entity |
| Predicate | corporateTeamOf |
P173540
|
FINISHED |
| Object | Suntory |
—
|
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: Suntory | Statement: [Suntory Sungoliath, corporateTeamOf, Suntory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: corporateTeamOf Context triple: [Suntory Sungoliath, corporateTeamOf, Suntory]
-
A.
associatedTeam
Indicates that one entity is linked or connected to a particular team, typically as its member, owner, or primary affiliation.
-
B.
coreTeams
Indicates that the entities are part of the same primary or central team within an organization or project.
-
C.
associatedTeamPrincipal
Indicates that there is a relationship in which a specific team principal is linked or connected to a particular team.
-
D.
memberTeam
Indicates that an entity belongs to or is part of a specific team.
-
E.
fieldsTeam
Indicates that an entity is a member of, or associated as part of, a particular team.
- 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b63f9da88190975712a5644500c7 |
completed | May 3, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:25 a.m.