Triple
T805184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ChatGPT Plus |
E17414
|
entity |
| Predicate | hasAdvantageOver |
P635
|
FINISHED |
| Object | free ChatGPT tier |
—
|
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: free ChatGPT tier | Statement: [ChatGPT Plus, hasAdvantageOver, free ChatGPT tier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdvantageOver Context triple: [ChatGPT Plus, hasAdvantageOver, free ChatGPT tier]
-
A.
hasAdvantage
chosen
Indicates that one entity possesses a benefit, edge, or favorable position over another in a given context.
-
B.
notableAdvantage
Indicates that one entity possesses a significant benefit, edge, or favorable quality over another entity or in a given context.
-
C.
homeFieldAdvantage
Indicates that one participant benefits from playing or operating in a familiar or home environment, gaining an advantage over the opponent.
-
D.
winnerThrows
Indicates that the entity identified as the winner performs or executes a throw action toward or involving another entity.
-
E.
wonFor
Indicates that one entity received an award, prize, or recognition specifically on behalf of or representing another entity.
- 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_69a4937ae8a08190b5084a03d532b30e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ace495348190aec66f35ea90bc89 |
completed | March 1, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69a4aa70973c8190adbf08302d1103a9 |
completed | March 1, 2026, 9:06 p.m. |
Created at: March 1, 2026, 7:38 p.m.