Triple
T33026120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banu Yam |
E845046
|
entity |
| Predicate | modernDistribution |
P29815
|
FINISHED |
| Object | Najran Province |
—
|
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: Najran Province | Statement: [Banu Yam, modernDistribution, Najran Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernDistribution Context triple: [Banu Yam, modernDistribution, Najran Province]
-
A.
currentDistribution
chosen
Indicates the way something is presently allocated, spread, or shared among a set of entities or locations.
-
B.
previousDistribution
Indicates that one distribution event or state occurred immediately before another in a sequence.
-
C.
targetDistribution
Indicates the intended allocation or spread of something (such as resources, data, or outputs) across specified targets or recipients.
-
D.
distributedAs
Indicates that something is allocated, delivered, or spread out according to a particular pattern, rule, or distribution scheme.
-
E.
officialDistributionOf
Indicates an authorized or formally sanctioned distribution relationship, where one entity is responsible for officially providing or disseminating something to others.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: May 1, 2026, 1:23 a.m.