Triple
T20045391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pichu |
E497543
|
entity |
| Predicate | baseExperienceYield |
P62973
|
FINISHED |
| Object | 41 |
—
|
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: 41 | Statement: [Pichu, baseExperienceYield, 41]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baseExperienceYield Context triple: [Pichu, baseExperienceYield, 41]
-
A.
commandExperience
Indicates that an entity has experience or a track record in holding command or leadership roles over others.
-
B.
providesExperienceOf
Indicates that one entity enables or delivers the experience of another entity to someone or something.
-
C.
settingOfExperience
Indicates that a particular context, environment, or situation serves as the backdrop or circumstances in which an experience occurs.
-
D.
experienceDuration
Indicates the length of time over which an entity undergoes or has undergone a particular experience or event.
-
E.
pointsEarnedFrom
chosen
Indicates the number of points that an entity has received as a result of another specified source, action, or event.
- 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_69da627278c88190babe4297a9df1236 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e662eea09481908d1001165e9d719c |
completed | April 20, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:37 p.m.