Triple
T31557962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4th Light Horse Regiment |
E805177
|
entity |
| Predicate | garrisonedInTheatre |
P19869
|
FINISHED |
| Object | Sinai Peninsula |
—
|
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: Sinai Peninsula | Statement: [4th Light Horse Regiment, garrisonedInTheatre, Sinai Peninsula]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: garrisonedInTheatre Context triple: [4th Light Horse Regiment, garrisonedInTheatre, Sinai Peninsula]
-
A.
garrisonOrTheater
Indicates that one entity serves as a military garrison or theater of operations for another entity.
-
B.
garrisonIncluded
Indicates that a particular garrison is included within, or forms part of, a specified larger military force, unit, or installation.
-
C.
garrisonedDuring
Indicates that a military force was stationed or quartered at a location for defense or control during a specified time period.
-
D.
garrisonOrAssemblyArea
chosen
Indicates a location where military forces are stationed, housed, or gathered for organization, preparation, or deployment.
-
E.
garrisonDuringBattle
Indicates that an entity is stationed to defend or hold a location specifically during the time a battle is taking place.
- 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8055f8081908f635fe04654b5fe |
completed | May 3, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:13 p.m.