Triple
T37661948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Villager (Minecraft) |
E937735
|
entity |
| Predicate | gainsExperienceFrom |
P29970
|
FINISHED |
| Object | successful trades |
—
|
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: successful trades | Statement: [Villager (Minecraft), gainsExperienceFrom, successful trades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gainsExperienceFrom Context triple: [Villager (Minecraft), gainsExperienceFrom, successful trades]
-
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.
gainsAbility
Indicates that one entity comes to acquire or develop a new ability as a result of another entity or event.
-
D.
experiencedByCharacter
Indicates that a particular event, situation, or emotion is undergone or lived through by a specific character.
-
E.
gainedBy
chosen
Indicates that something comes to possess, obtain, or receive something else as a result of an action, process, 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.