Triple
T37550729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huojin pandaren |
E933584
|
entity |
| Predicate | alignmentChoiceFor |
P188717
|
FINISHED |
| Object | playable pandaren |
—
|
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: playable pandaren | Statement: [Huojin pandaren, alignmentChoiceFor, playable pandaren]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alignmentChoiceFor Context triple: [Huojin pandaren, alignmentChoiceFor, playable pandaren]
-
A.
alignmentUsage
Indicates how an entity’s alignment, orientation, or positioning is applied or utilized in relation to another entity or context.
-
B.
alignmentMethod
Indicates the technique or procedure used to align one entity with another or with a reference standard.
-
C.
alignedAgainst
Indicates that two or more entities are united in opposition to a common target, side, or objective.
-
D.
alignmentGoal
Indicates that an entity has a desired or target alignment state it aims to achieve or maintain.
-
E.
coordinateChoice
Indicates that one option is selected from a set of mutually exclusive alternatives within a coordinated choice structure.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbacaea12c8190a4c99e64335f0e7e |
completed | May 6, 2026, 9:03 p.m. |
Created at: May 3, 2026, 4:17 p.m.