Triple
T26493891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Order 191 |
E669227
|
entity |
| Predicate | orderedMovementToward |
P96531
|
FINISHED |
| Object | Boonsboro, Maryland |
—
|
NE NERFINISHED |
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: Boonsboro, Maryland | Statement: [Special Order 191, orderedMovementToward, Boonsboro, Maryland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderedMovementToward Context triple: [Special Order 191, orderedMovementToward, Boonsboro, Maryland]
-
A.
orderedToward
chosen
Indicates that one entity is arranged, directed, or positioned in the direction of another entity or reference point.
-
B.
movementFor
Indicates that one entity moves on behalf of, in support of, or as a representative action for another entity.
-
C.
movementDirection
Indicates the direction or path along which an entity moves or is moving relative to a reference frame or point.
-
D.
movementIn
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
-
E.
movementOrderedBy
Indicates that one entity’s movement occurs according to, or is arranged/controlled by, another entity’s ordering or directive.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 1:06 a.m.