Triple
T24580761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PNG Kumuls |
E608241
|
entity |
| Predicate | fanSupportLevel |
P59318
|
FINISHED |
| Object | very high |
—
|
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: very high | Statement: [PNG Kumuls, fanSupportLevel, very high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanSupportLevel Context triple: [PNG Kumuls, fanSupportLevel, very high]
-
A.
fanInterestLevel
chosen
Indicates the degree or intensity of enthusiasm or interest that a fan has toward a particular subject, such as a person, team, or work.
-
B.
fanOwned
Indicates that the entity is owned or controlled by fans, typically through collective or community-based ownership rather than traditional private or corporate ownership.
-
C.
fanAccess
Indicates that an entity has permission or the ability to access fan-related content, features, or areas associated with another entity.
-
D.
fanTerm
Indicates that one entity is a term, label, or expression used by fans to refer to or describe another entity.
-
E.
fanDestination
Indicates that one entity is the intended target or recipient of another entity’s enthusiasm, admiration, or fandom.
- 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_69e2c4ce89248190ad99e18f0638dfbb |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a982db00819081038adce05c0b52 |
completed | April 30, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:29 a.m.