Triple
T1100185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mission San Luis Rey de Francia |
E24359
|
entity |
| Predicate | sequenceInCaliforniaMissions |
P24122
|
FINISHED |
| Object | 18 |
—
|
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: 18 | Statement: [Mission San Luis Rey de Francia, sequenceInCaliforniaMissions, 18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sequenceInCaliforniaMissions Context triple: [Mission San Luis Rey de Francia, sequenceInCaliforniaMissions, 18]
-
A.
CaliforniaHistoricalLandmarkNumber
Indicates that an entity has been assigned a specific official California Historical Landmark identification number.
-
B.
rankInCaliforniaByPopulation
Indicates the ordinal position of an entity in a list of California entities ordered by their population size.
-
C.
distanceFromMonterey
Indicates the measured distance between a given entity’s location and the location of Monterey.
-
D.
sequenceInBeagleVoyages
Indicates that one event, observation, or item occurs at a specific position within the ordered sequence of Beagle voyages.
-
E.
numberOfMissions
Indicates the total count of missions associated with a given entity or context.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9be92688190838ce35cd67e01f3 |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b745ef3481909a7ce4647c8567b3 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b8f1097881908932d7eea4331917 |
completed | March 1, 2026, 10:08 p.m. |
Created at: March 1, 2026, 7:43 p.m.