Triple
T6718467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muharram |
E153332
|
entity |
| Predicate | forbiddenActsHistorically |
P9816
|
FINISHED |
| Object | fighting |
—
|
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: fighting | Statement: [Muharram, forbiddenActsHistorically, fighting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forbiddenActsHistorically Context triple: [Muharram, forbiddenActsHistorically, fighting]
-
A.
historicalLaw
Indicates that the referenced law or legal provision existed and was in effect during a past historical period, rather than being current.
-
B.
historicalPractice
chosen
Indicates that an action, behavior, or relationship occurred as a customary or established practice during a past historical period.
-
C.
wasOnceOutlawed
Indicates that an entity was previously considered illegal or banned by an authority but is no longer outlawed.
-
D.
historicallyImposed
Indicates that one entity has enforced, established, or applied something upon another in the past, typically through authority, power, or institutional action.
-
E.
historicallyConsidered
Indicates that one entity has been regarded or classified in a particular way relative to another entity during a past historical period.
- 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_69c68809b4608190a2509ddb5ab87f05 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d135d27c819088c45839ad0e7bab |
completed | March 27, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69c6d08c5d348190a29dee668c398e70 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:07 p.m.