Triple
T3672079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | marja'iyya |
E77902
|
entity |
| Predicate | financing |
P37457
|
FINISHED |
| Object | religious taxes (khums) |
—
|
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: religious taxes (khums) | Statement: [marja'iyya, financing, religious taxes (khums)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: financing Context triple: [marja'iyya, financing, religious taxes (khums)]
-
A.
funds
Indicates that one entity provides financial resources or monetary support to another entity or activity.
-
B.
finType
Indicates that an entity is of a finite type, meaning it has only a finite number of distinct possible values or elements.
-
C.
fundingContext
chosen
Indicates the circumstances, purpose, or conditions under which funding is provided or used in a given relationship or action.
-
D.
investment
Indicates a relationship where one party allocates resources (such as money, time, or effort) into something with the expectation of future benefit or return.
-
E.
finStructure
Indicates a relationship where one entity specifies or characterizes the fin-related structural features or configuration of another entity.
- 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_69ad85e083008190b2e1b7085fe500bd |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc42de1bc819090e19dd0805f13a1 |
completed | March 8, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69adb84a20288190a092e4a1b045fe3f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.