Triple
T3516966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presidio of San Francisco |
E74330
|
entity |
| Predicate | transferredIn |
P21042
|
FINISHED |
| Object | 1846 |
—
|
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: 1846 | Statement: [Presidio of San Francisco, transferredIn, 1846]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferredIn Context triple: [Presidio of San Francisco, transferredIn, 1846]
-
A.
hasTransfer
Indicates a relationship where something is moved or conveyed from one entity or location to another.
-
B.
transferAfter
Indicates that one entity transfers something to another entity only after a specified event or condition has occurred.
-
C.
functionTransferredTo
Indicates that a specific function, role, or responsibility has been moved from one entity to another.
-
D.
transferredRegion
chosen
Indicates that control, ownership, or responsibility for a geographic or administrative region has been moved from one entity to another.
-
E.
transferType
Indicates the specific method or category of how something is transferred from one entity to another.
- 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_69ad85cfb5c881909c9a2edd9d6043cc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc31c0688190a890621a901f5f5f |
completed | March 8, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69adae10689c8190b7dc6d7daa8295b6 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.