Triple
T290651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Number One Observatory Circle |
E5983
|
entity |
| Predicate | laterFunction |
P9424
|
FINISHED |
| Object | residence of the Chief of Naval Operations |
—
|
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: residence of the Chief of Naval Operations | Statement: [Number One Observatory Circle, laterFunction, residence of the Chief of Naval Operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterFunction Context triple: [Number One Observatory Circle, laterFunction, residence of the Chief of Naval Operations]
-
A.
formerFunction
Indicates that an entity previously held a specific role, position, or function but no longer does so.
-
B.
assignedFunction
Indicates that a specific role, duty, or function has been formally allocated to an entity.
-
C.
laterPerception
Indicates that one entity’s perception, awareness, or observation of something occurs after another specified time, event, or perception.
-
D.
secondaryFunction
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
-
E.
laterMember
Indicates that one entity became a member of a group or organization at a later time than another entity.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e4f78bc81909a64fd6aaec3b504 |
completed | Feb. 28, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69a25b7d089081909810442c3d0182f6 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25d0ec71081908478c800be4f7bb0 |
completed | Feb. 28, 2026, 3:12 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.