Triple
T29341508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jade Empire |
E744048
|
entity |
| Predicate | alignmentSystem |
P167133
|
FINISHED |
| Object | Open Palm and Closed Fist |
—
|
NE NERFINISHED |
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: Open Palm and Closed Fist | Statement: [Jade Empire, alignmentSystem, Open Palm and Closed Fist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alignmentSystem Context triple: [Jade Empire, alignmentSystem, Open Palm and Closed Fist]
-
A.
alignmentControl
Indicates that one entity manages, adjusts, or enforces the positional or structural alignment of another entity.
-
B.
alignmentComponents
Indicates that one entity is composed of or associated with specific subparts or elements that together form its overall alignment.
-
C.
alignmentGoal
Indicates that an entity has a desired or target alignment state it aims to achieve or maintain.
-
D.
alignmentConcept
Indicates a conceptual or abstract relationship of alignment or correspondence between entities, such as agreement, compatibility, or shared orientation in some dimension.
-
E.
alignmentMethod
Indicates the technique or procedure used to align one entity with another or with a reference standard.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f66926e7a48190a1b580fd9fe67c31 |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 28, 2026, 1:34 p.m.