Triple
T29655410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Templar Archives |
E750249
|
entity |
| Predicate | enablesUnit |
P103504
|
FINISHED |
| Object | High Templar |
—
|
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: High Templar | Statement: [Templar Archives, enablesUnit, High Templar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enablesUnit Context triple: [Templar Archives, enablesUnit, High Templar]
-
A.
authorizedUnit
Indicates that one entity is officially permitted or empowered to act on behalf of, or perform certain actions for, another entity or system.
-
B.
enablingInstrument
chosen
Indicates that one entity serves as the means, tool, or instrument that enables another entity’s action or effect to occur.
-
C.
enablingPowerFor
Indicates that one entity provides the capability or authority that allows another entity to perform a specific function, action, or role.
-
D.
supportedUnit
Indicates that one entity provides assistance, resources, or backing to another entity functioning as a unit or sub-organization.
-
E.
enablesService
Indicates that one entity provides the capability or necessary conditions for another entity to offer or perform a specific service.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 28, 2026, 6:54 p.m.