Triple
T10285399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casablanca, French Morocco |
E241212
|
entity |
| Predicate | hadGarrisonOf |
P13834
|
FINISHED |
| Object | French colonial troops |
—
|
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: French colonial troops | Statement: [Casablanca, French Morocco, hadGarrisonOf, French colonial troops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadGarrisonOf Context triple: [Casablanca, French Morocco, hadGarrisonOf, French colonial troops]
-
A.
garrisonTown
Indicates that a town serves as a military base or station where armed forces are permanently or regularly housed.
-
B.
laterGarrisonedBy
chosen
Indicates that a location or structure was subsequently occupied and used as a military garrison by a specified force or group.
-
C.
garrisonedDuring
Indicates that a military force was stationed or quartered at a location for defense or control during a specified time period.
-
D.
garrisonOrHQ
Indicates that an entity serves as a military garrison or headquarters location for another entity.
-
E.
garrisonOrAssemblyArea
Indicates a location where military forces are stationed, housed, or gathered for organization, preparation, or deployment.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f117708190928f92ae2611d724 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:40 a.m.