Triple
T31994310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sudan Gezira Board |
E816952
|
entity |
| Predicate | scaleOfProjectManaged |
P166384
|
FINISHED |
| Object | large-scale irrigated agriculture |
—
|
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: large-scale irrigated agriculture | Statement: [Sudan Gezira Board, scaleOfProjectManaged, large-scale irrigated agriculture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scaleOfProjectManaged Context triple: [Sudan Gezira Board, scaleOfProjectManaged, large-scale irrigated agriculture]
-
A.
projectTypeManaged
chosen
Indicates that an entity is responsible for overseeing or administering a particular type or category of project.
-
B.
overseesProject
Indicates that one entity has responsibility for supervising, managing, or directing the progress and execution of a project involving another entity.
-
C.
projectLength
Indicates the duration or total time span over which a project is planned or executed.
-
D.
managedIn
Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of another entity.
-
E.
numberOfMajorProjects
Indicates the count of significant or primary projects associated with an entity.
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:13 a.m.