Triple
T4871407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knights Templar |
E109091
|
entity |
| Predicate | suppressedInYear |
P28109
|
FINISHED |
| Object | 1312 |
—
|
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: 1312 | Statement: [Knights Templar, suppressedInYear, 1312]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suppressedInYear Context triple: [Knights Templar, suppressedInYear, 1312]
-
A.
suppressionYear
chosen
Indicates the year in which the referenced activity, expression, or entity was formally suppressed, halted, or forcibly discontinued.
-
B.
suppressedInCountry
Indicates that an entity (such as content, activity, or information) is restricted, censored, or otherwise prevented from being available or expressed within a specified country.
-
C.
suppressedDuring
Indicates that one event, action, or state is actively prevented, inhibited, or held back while another specified event, condition, or time period is occurring.
-
D.
censorshipYear
Indicates the year in which an act of censorship was imposed on the referenced content or entity.
-
E.
suppressedFollowing
Indicates that one entity’s act of following another has been intentionally hidden, blocked, or not allowed to occur.
- 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_69bd440d96a48190b0c87069adef2af1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c28e56081908ee411ac94c3769e |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:27 p.m.