Triple
T10927578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacobus Vanderveer House |
E258109
|
entity |
| Predicate | functionDuringWar |
P19322
|
FINISHED |
| Object | military headquarters vicinity |
—
|
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: military headquarters vicinity | Statement: [Jacobus Vanderveer House, functionDuringWar, military headquarters vicinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionDuringWar Context triple: [Jacobus Vanderveer House, functionDuringWar, military headquarters vicinity]
-
A.
functionDuringBattle
Indicates a functional role, effect, or behavior that specifically occurs or is active during a battle.
-
B.
operatorDuringWar
Indicates that an entity operated or was active in its role during a time of war.
-
C.
functionDuringRevolution
Indicates that an entity performs or serves a particular function specifically during a revolutionary period or event.
-
D.
functionDuringReign
Indicates that a function, role, or activity occurred or was performed during the time span of a particular ruler’s reign.
-
E.
statusDuringWar
chosen
Indicates the role, condition, or classification an entity held specifically during a period of war.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7709da23c819096f4bba1cd4ff5cb |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d72e799f808190b6ab64fc7586a303 |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:22 p.m.