Triple
T3340653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruwaard of Putten |
E70249
|
entity |
| Predicate | positionStatus |
P127
|
FINISHED |
| Object | defunct office |
—
|
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: defunct office | Statement: [Ruwaard of Putten, positionStatus, defunct office]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionStatus Context triple: [Ruwaard of Putten, positionStatus, defunct office]
-
A.
positionInState
Indicates that one entity occupies or holds a specific position, role, or status within a particular state or condition of another entity.
-
B.
designationStatus
Indicates the current official classification or standing assigned to an entity within a defined system or process.
-
C.
status
chosen
Indicates the current condition, state, or standing of an entity within a given context.
-
D.
coordinateStatus
Indicates that one entity’s status is aligned, synchronized, or made consistent with another entity’s status or with a shared reference state.
-
E.
careerStatus
Indicates the current stage, position, or condition of an entity within its professional or occupational life.
- 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_69ad85a405e48190b6e68de7cf9f319e |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb1c0ae44819091c851569eaf4565 |
completed | March 8, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69ada42c2ba8819091136805ce17b39d |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.