Triple
T1094301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mission San Gabriel Arcángel |
E24236
|
entity |
| Predicate | orderInMissionChain |
P23808
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Mission San Gabriel Arcángel, orderInMissionChain, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderInMissionChain Context triple: [Mission San Gabriel Arcángel, orderInMissionChain, 4]
-
A.
overseesMission
Indicates that one entity has responsibility for supervising, directing, or managing the execution of a mission undertaken by another entity.
-
B.
subsequentOrder
Indicates that one order occurs after or follows another order in sequence.
-
C.
establishedInOrder
Indicates that one entity was created, founded, or formally set up as a result of, or in accordance with, a specific order, directive, or mandate.
-
D.
isPartOfChainOfCommand
Indicates that one entity holds a position within a hierarchical authority structure in which it is subordinate to, or otherwise organized under, another entity in the chain of command.
-
E.
orderPrecedence
Indicates that one entity must come before another in a defined sequence or priority order.
- 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_69a4b99d1e8c81909cf1178d68d38885 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b743175481908f3967e589717c55 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b80f0fb08190a19a50e38ae8f16c |
completed | March 1, 2026, 10:05 p.m. |
Created at: March 1, 2026, 7:42 p.m.