Triple
T30772556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sudanese states |
E783565
|
entity |
| Predicate | collect |
P2196
|
FINISHED |
| Object | certain local taxes and fees |
—
|
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: certain local taxes and fees | Statement: [Sudanese states, collect, certain local taxes and fees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collect Context triple: [Sudanese states, collect, certain local taxes and fees]
-
A.
collects
chosen
Indicates that one entity gathers, accumulates, or brings together one or more other entities into its possession or control.
-
B.
collectionBy
Indicates that one entity is the collector or curator responsible for assembling, managing, or owning a particular collection of items represented by another entity.
-
C.
collectsFrom
Indicates that one entity gathers, receives, or takes something (such as items, data, or payments) from another entity.
-
D.
collectionFormed
Indicates that multiple items or entities have been gathered and organized together into a defined collection.
-
E.
gathering
Indicates that one or more entities are coming together or being brought together into a group at a particular time or 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: April 29, 2026, 8:40 p.m.