Triple
T33886847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arab-Berber civilization |
E868654
|
entity |
| Predicate | coreAreasInclude |
P171192
|
FINISHED |
| Object | Morocco |
—
|
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: Morocco | Statement: [Arab-Berber civilization, coreAreasInclude, Morocco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreAreasInclude Context triple: [Arab-Berber civilization, coreAreasInclude, Morocco]
-
A.
competenceArea
Indicates that one entity has a particular domain, field, or area in which it possesses competence, expertise, or responsibility.
-
B.
coreAreaOf
Indicates that one entity is the central, primary, or most important area or domain of focus for another entity.
-
C.
coreAreaNowIn
chosen
Indicates that an entity’s primary or central area is currently located within or part of another specified area.
-
D.
coreCategory
Indicates that one entity is the primary or fundamental category to which another entity belongs or is classified under.
-
E.
strategicArea
Indicates that an entity is designated as an area of strategic importance or priority within a broader plan, operation, or context.
- 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_69f34996761c8190864e42f7c9cf215b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:48 a.m.