Triple
T31439604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogueport Pianta Parlor |
E802030
|
entity |
| Predicate | offersReward |
P50170
|
FINISHED |
| Object | badges |
—
|
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: badges | Statement: [Rogueport Pianta Parlor, offersReward, badges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersReward Context triple: [Rogueport Pianta Parlor, offersReward, badges]
-
A.
offersRewardFor
Indicates that one entity promises or provides a reward in exchange for another entity performing a specified action or achieving a particular outcome.
-
B.
offersAward
chosen
Indicates that one entity grants or makes available an award or prize to another entity.
-
C.
offeredRewardTo
Indicates that one entity has proposed or promised a reward to another entity, typically as an incentive for a specific action or outcome.
-
D.
rewardOfferedBy
Indicates that a reward is provided or promised by one entity to another, typically as an incentive or compensation for a specific action or outcome.
-
E.
offersIncentive
Indicates that one entity provides a reward, benefit, or motivation to another entity to encourage a specific action or behavior.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: April 30, 2026, 9:04 p.m.