Triple
T6410404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mission San Luis Rey de Francia |
E127688
|
entity |
| Predicate | onceHadStatus |
P39943
|
FINISHED |
| Object | largest mission in Alta California |
—
|
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: largest mission in Alta California | Statement: [Mission San Luis Rey de Francia, onceHadStatus, largest mission in Alta California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onceHadStatus Context triple: [Mission San Luis Rey de Francia, onceHadStatus, largest mission in Alta California]
-
A.
hadSpecialStatusIn
Indicates that an entity possessed a particular special, exceptional, or non-standard status within a specified context or time period.
-
B.
hasHad
chosen
Indicates that an entity previously experienced, possessed, or was involved in something at some point in the past.
-
C.
earlierStatus
Indicates that one status or condition occurred or was valid before another status in time.
-
D.
hadStateFrom
Indicates that an entity possessed or was in a particular state starting from a specified point in time.
-
E.
status
Indicates the current condition, state, or standing of an entity within a given context.
- 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_69c0083723d88190b1e37b19df162c08 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068cf81508190bc09e58ec45bc858 |
completed | March 22, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69c060f40ecc8190b1df17b96767675c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:41 p.m.