Triple
T5133780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old State, War, and Navy Building |
E115766
|
entity |
| Predicate | builtIn19thCentury |
P62809
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Old State, War, and Navy Building, builtIn19thCentury, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtIn19thCentury Context triple: [Old State, War, and Navy Building, builtIn19thCentury, true]
-
A.
compiledInCentury
Indicates that something (such as a work, text, or document) was compiled during a specified century.
-
B.
declaredInCentury
Indicates that something (such as an event, work, or concept) was formally declared or proclaimed during a specified century.
-
C.
acquiredInCentury
Indicates that one entity was acquired during a specific century represented by the other entity.
-
D.
collectionEndCentury
Indicates the century in which a collection or collecting activity came to an end.
-
E.
introducedInCentury
Indicates the century during which something (such as an idea, technology, practice, or entity) was first introduced or came into use.
- 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_69bd444426bc819099ccd23f141e22aa |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7fef2e8c8190982dd67f50295ada |
completed | March 20, 2026, 5:12 p.m. |
| PD | Predicate disambiguation | batch_69bd77ac2fc48190abeebb003a82384c |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd7fee42748190967013828973cce0 |
completed | March 20, 2026, 5:12 p.m. |
Created at: March 20, 2026, 1:43 p.m.