Triple
T29397930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franco-Moroccan War (1844) |
E745552
|
entity |
| Predicate | usedByMorocco |
P180330
|
FINISHED |
| Object | Moroccan regular forces |
—
|
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: Moroccan regular forces | Statement: [Franco-Moroccan War (1844), usedByMorocco, Moroccan regular forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByMorocco Context triple: [Franco-Moroccan War (1844), usedByMorocco, Moroccan regular forces]
-
A.
partyRoleOfMorocco
Indicates that an entity holds a specific party role or status in relation to Morocco.
-
B.
MoroccanStrengthApprox
Indicates an approximate assessment or estimation of the strength associated with Morocco or Moroccan-related entities.
-
C.
MoroccanConcession
Indicates a diplomatic or commercial concession granted in the context of Moroccan affairs or territory.
-
D.
moroccoEliminated
Indicates that Morocco has been removed from further participation or contention, typically by losing in a competitive context such as a tournament or qualification process.
-
E.
goalsByMorocco
Indicates the number of goals that were scored by Morocco.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
| PDg | Predicate description generation | batch_69f73adfd9a081908adae6bd59dfefb9 |
completed | May 3, 2026, 12:09 p.m. |
Created at: April 28, 2026, 2:48 p.m.