Triple
T17445183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mei |
E424761
|
entity |
| Predicate | survivalSkill |
P66149
|
FINISHED |
| Object | hand-to-hand combat |
—
|
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: hand-to-hand combat | Statement: [Mei, survivalSkill, hand-to-hand combat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivalSkill Context triple: [Mei, survivalSkill, hand-to-hand combat]
-
A.
helpsSurvive
chosen
Indicates that one entity provides support or advantage that increases another entity’s chances of survival.
-
B.
survivesExpedition
Indicates that an entity endures and remains alive through the duration of a specified expedition or journey.
-
C.
survivesShipwreck
Indicates that an entity continues to live or remain alive after experiencing a shipwreck.
-
D.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
-
E.
hunting
Indicates one entity actively pursuing and attempting to capture or kill another entity, typically as prey.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44ffafec48190b25980318cea353f |
completed | April 19, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.