Triple
T29267982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Undang (territorial chief) |
E742027
|
entity |
| Predicate | hasTitleHolderGenderTradition |
P20413
|
FINISHED |
| Object | male |
—
|
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: male | Statement: [Undang (territorial chief), hasTitleHolderGenderTradition, male]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleHolderGenderTradition Context triple: [Undang (territorial chief), hasTitleHolderGenderTradition, male]
-
A.
hasGenderedTitle
Indicates that an entity is associated with a title or form of address that is explicitly marked for a particular gender.
-
B.
hasGenderInSomeTraditions
chosen
Indicates that, in at least some cultural, religious, or historical traditions, the subject is regarded as having a specific gender.
-
C.
titleHolderSex
Indicates the biological or identified sex of the person who holds a particular title.
-
D.
hasGenderConvention
Indicates that there is an established or customary way of assigning or expressing gender within a given context, system, or culture.
-
E.
honorificGender
Indicates that a particular honorific or title is associated with a specific gender or gendered form.
- 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_69f0912124d48190a046642b69407f4c |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 28, 2026, 12:46 p.m.