Triple
T17322924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burggraf |
E420604
|
entity |
| Predicate | officeIncludes |
P127000
|
FINISHED |
| Object | command of castle garrison |
—
|
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: command of castle garrison | Statement: [Burggraf, officeIncludes, command of castle garrison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeIncludes Context triple: [Burggraf, officeIncludes, command of castle garrison]
-
A.
defaultOfficeSuite
Indicates that a particular office software suite is set as the primary or standard choice to be used by default.
-
B.
supportsOffice
Indicates that one entity provides assistance, resources, or endorsement to an office or officeholder in performing its functions or maintaining its operations.
-
C.
requiresOffice
Indicates that performing or fulfilling the related activity, role, or condition depends on being in or having access to a physical office location.
-
D.
officeTerm
Indicates the period of time during which an individual officially holds a particular position or office.
-
E.
officeAction
Indicates an official act or decision taken by an office or authority in response to a matter, request, or proceeding.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e439d0cf2481908a018593ef39fd18 |
completed | April 19, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:43 a.m.