Triple
T25074127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MFO |
E628000
|
entity |
| Predicate | hasSectorHQ |
P141133
|
FINISHED |
| Object | North Camp, El Gorah, Sinai |
—
|
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: North Camp, El Gorah, Sinai | Statement: [MFO, hasSectorHQ, North Camp, El Gorah, Sinai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSectorHQ Context triple: [MFO, hasSectorHQ, North Camp, El Gorah, Sinai]
-
A.
hasHeadquartersRoleFor
Indicates that an entity holds a specific role or position within the headquarters of another entity.
-
B.
hasHeadquartersType
Indicates the specific kind or classification of headquarters associated with an entity.
-
C.
hasHigherHeadquarters
Indicates that one organizational unit serves as the superior or parent headquarters overseeing another unit.
-
D.
hasHeadquartersFunctionFor
chosen
Indicates that an entity serves as the central coordinating or managing headquarters for another entity’s operations or activities.
-
E.
hasOwnerHeadquartersIn
Indicates that the owning entity’s main headquarters is located in the specified 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 18, 2026, 6:20 a.m.