Triple
T24348848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nigerian Air Force Military School, Jos |
E613725
|
entity |
| Predicate | primaryIntakeSource |
P13353
|
FINISHED |
| Object | boys from across Nigeria |
—
|
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: boys from across Nigeria | Statement: [Nigerian Air Force Military School, Jos, primaryIntakeSource, boys from across Nigeria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryIntakeSource Context triple: [Nigerian Air Force Military School, Jos, primaryIntakeSource, boys from across Nigeria]
-
A.
primaryIntakeType
Indicates the main or most significant type of intake or input associated with an entity or process.
-
B.
primaryIntake
chosen
Indicates that one entity serves as the main or first point of intake, reception, or admission for another entity.
-
C.
primarySourceArea
Indicates that something originates from, or is chiefly derived from, a specified source area.
-
D.
primaryReceptionMethod
Indicates the main way in which something is received, accessed, or obtained among multiple possible methods.
-
E.
primaryIntent
Indicates the main purpose, goal, or motivation underlying an action, event, or relationship among entities.
- 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_69e2d7ddd29481909e7f539a6072bd71 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293430524819087984a699d1d3687 |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:58 a.m.