Triple
T3575715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | President's House (original design) |
E75682
|
entity |
| Predicate | functionIntended |
P13995
|
FINISHED |
| Object | official residence |
—
|
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: official residence | Statement: [President's House (original design), functionIntended, official residence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionIntended Context triple: [President's House (original design), functionIntended, official residence]
-
A.
intendedFunction
chosen
Indicates that something is designed or purposed to perform a particular role, use, or function.
-
B.
usesFunction
Indicates that one entity employs, invokes, or relies on a particular function to perform an operation or achieve a result.
-
C.
endedFunctionallyWith
Indicates that a process, event, or relationship has effectively concluded in practice, even if it has not been formally or officially terminated.
-
D.
hasIntendedEffect
Indicates that one entity is expected or designed to produce a particular effect or outcome on another entity or context.
-
E.
definesFunctioningOf
Indicates that one entity specifies or determines how another entity operates or functions.
- 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_69ad85d5e3008190bdfe0bacdd1f5a1b |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0da77008190922f414b85b9cad4 |
completed | March 8, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69adb83810c481909c645c08b978edc1 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.