Triple
T29129483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghadamisi |
E738330
|
entity |
| Predicate | secondaryDomainOfUse |
P180307
|
FINISHED |
| Object | oral tradition and folklore |
—
|
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: oral tradition and folklore | Statement: [Ghadamisi, secondaryDomainOfUse, oral tradition and folklore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryDomainOfUse Context triple: [Ghadamisi, secondaryDomainOfUse, oral tradition and folklore]
-
A.
secondaryDomain
Indicates that one domain functions as a secondary or auxiliary domain in relation to a primary domain.
-
B.
secondaryAreaOfUse
chosen
Indicates that an entity has an additional, non-primary context, domain, or purpose in which it is used.
-
C.
secondaryLandUse
Indicates a secondary or additional way in which a piece of land is used, beyond its primary designated use.
-
D.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
E.
secondarySite
Indicates that one entity serves as an additional or subordinate location associated with another primary site.
- 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_69f07cb29cdc8190afa55444553de60c |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: April 28, 2026, 11:30 a.m.