Triple
T12727679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secret Annex |
E304147
|
entity |
| Predicate | dateFirstOccupied |
P71101
|
FINISHED |
| Object | 1942-07-06 |
—
|
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: 1942-07-06 | Statement: [Secret Annex, dateFirstOccupied, 1942-07-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateFirstOccupied Context triple: [Secret Annex, dateFirstOccupied, 1942-07-06]
-
A.
firstOccupied
Indicates that an entity was the initial or earliest occupant of a particular place, position, or resource.
-
B.
occupationDate
chosen
Indicates the date or time period during which an entity assumes, holds, or begins a particular role, position, or occupation.
-
C.
firstOccupiedBy
Indicates which entity was the initial or earliest known occupant of a given place, position, or resource.
-
D.
timePeriodOfEarlierOccupation
Indicates that one entity specifies the time span during which another entity was previously occupied or held a position before a later occupation.
-
E.
hasEvidenceOfOccupationSince
Indicates that there is evidence showing an entity has been occupied continuously or intermittently since a specified point in time.
- 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:25 p.m.