Triple
T27545774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iran women's national football team |
E695355
|
entity |
| Predicate | religiousDressCode |
P2738
|
FINISHED |
| Object | hijab |
—
|
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: hijab | Statement: [Iran women's national football team, religiousDressCode, hijab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousDressCode Context triple: [Iran women's national football team, religiousDressCode, hijab]
-
A.
hasDressCode
chosen
Indicates that a specified entity enforces or is associated with a particular set of rules governing appropriate clothing or attire.
-
B.
religiousRestriction
Indicates that one entity imposes, experiences, or is subject to limitations or rules based on religious beliefs or practices in relation to another entity or context.
-
C.
hasClericalVestments
Indicates that one entity possesses or is associated with the clerical vestments (religious garments) of another entity.
-
D.
monasticDress
Indicates that an entity wears or is characterized by clothing associated with a monastic or religious order.
-
E.
wearingConvention
Indicates that an entity is dressed in accordance with a particular convention, style, or dress code.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: April 27, 2026, 1:33 p.m.