Triple
T36954300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athena’s Fortune |
E914149
|
entity |
| Predicate | hasReputationLevelCap |
P205661
|
FINISHED |
| Object | 20 |
—
|
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: 20 | Statement: [Athena’s Fortune, hasReputationLevelCap, 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReputationLevelCap Context triple: [Athena’s Fortune, hasReputationLevelCap, 20]
-
A.
hasRestrictionLevel
Indicates that an entity is subject to a specified degree or category of limitation, control, or access restriction.
-
B.
hasMaximumBalanceLimit
Indicates that there is an upper bound on the balance that an account or entity is allowed to hold.
-
C.
hasReputationScope
Indicates that a reputation or standing is specifically associated with, or limited to, a particular context, domain, or scope.
-
D.
reputationRankRequired
Indicates that a certain minimum reputation rank is required for an entity to access, perform, or qualify for the associated action or resource.
-
E.
hasTierRestriction
Indicates that an entity is limited or governed by specific access or service tiers, restricting what applies at each tier.
- 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:13 p.m.