Triple
T37554338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nightslayer Armor |
E933658
|
entity |
| Predicate | setNamePiecePattern |
P60600
|
FINISHED |
| Object | Nightslayer |
—
|
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: Nightslayer | Statement: [Nightslayer Armor, setNamePiecePattern, Nightslayer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setNamePiecePattern Context triple: [Nightslayer Armor, setNamePiecePattern, Nightslayer]
-
A.
namePattern
chosen
Indicates that an entity’s name follows or matches a specified pattern or format.
-
B.
namedAfterPattern
Indicates that one entity’s name is derived from or follows the naming convention or pattern established by another entity.
-
C.
nicknamePattern
Indicates that one entity serves as a nickname or informal name pattern for another entity.
-
D.
notationPattern
Indicates a recurring way in which something is symbolically represented or written, such as a consistent style or structure of notation used for an entity or concept.
-
E.
moduloPatternName
Indicates that an entity is associated with a specific naming pattern used for modulo-based grouping or partitioning.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba61dff5081909fec88a7aeb0c8a1 |
completed | May 6, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69fba350e9a8819095893229d9643572 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.