Triple
T36299693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashada month |
E893472
|
entity |
| Predicate | consideredInauspiciousFor |
P164103
|
FINISHED |
| Object | marriages in many regions |
—
|
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: marriages in many regions | Statement: [Ashada month, consideredInauspiciousFor, marriages in many regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consideredInauspiciousFor Context triple: [Ashada month, consideredInauspiciousFor, marriages in many regions]
-
A.
associatedUnluckyNumber
Indicates that an entity is linked to or characterized by a specific number considered unlucky.
-
B.
consideredOmenOf
Indicates that one entity is regarded as a sign or portent foretelling the occurrence or nature of another entity or event.
-
C.
superstitionType
Indicates the specific category or kind of superstition associated with an entity or belief.
-
D.
positionOnSuperstition
Indicates a stance, belief, or attitude that an entity holds regarding superstition or superstitious practices.
-
E.
notRecommendedIn
chosen
Indicates that something is advised against or discouraged from being used, done, or applied within a particular context, situation, or location.
- 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_69f76e4a61f0819084a2b68dbbb4efc6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.