Triple
T37515084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Templar |
E932613
|
entity |
| Predicate | startingAttributeBias |
P203030
|
FINISHED |
| Object | high Strength |
—
|
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: high Strength | Statement: [Templar, startingAttributeBias, high Strength]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startingAttributeBias Context triple: [Templar, startingAttributeBias, high Strength]
-
A.
initialAttitude
Indicates the starting stance, feeling, or disposition one entity holds toward another or toward a situation before any interaction or change occurs.
-
B.
typicalPositionBias
Indicates a systematic tendency for something to be placed, chosen, or interpreted in a commonly favored or default position relative to other options.
-
C.
perceivedAttribute
Indicates that one entity recognizes, interprets, or assigns a particular attribute or quality to another entity.
-
D.
favoredAttribute
Indicates that one entity prefers, prioritizes, or gives special positive weight to a particular attribute of another entity or object.
-
E.
coreAttribute
Indicates that one attribute is a fundamental, defining, or essential property of another entity.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0116ca6a1c81909a9e938dbe54eb8a |
completed | May 10, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_6a0116655e248190bdfe5b4bb4f1cf47 |
completed | May 10, 2026, 11:36 p.m. |
| PDg | Predicate description generation | batch_6a0116c9a0ac8190ae77f1c4ccd461ba |
completed | May 10, 2026, 11:37 p.m. |
Created at: May 3, 2026, 4:17 p.m.