Triple
T9095923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wahshi ibn Harb |
E218019
|
entity |
| Predicate | freedomCondition |
P87139
|
FINISHED |
| Object | to kill Hamza ibn Abd al-Muttalib |
—
|
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: to kill Hamza ibn Abd al-Muttalib | Statement: [Wahshi ibn Harb, freedomCondition, to kill Hamza ibn Abd al-Muttalib]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: freedomCondition Context triple: [Wahshi ibn Harb, freedomCondition, to kill Hamza ibn Abd al-Muttalib]
-
A.
releaseCondition
Indicates the circumstances or requirements under which something is allowed to be released or made available.
-
B.
positionOnFreedom
Indicates a stance or viewpoint an entity holds regarding the concept, extent, or conditions of freedom.
-
C.
freeFloatRequirement
Indicates that there is a specified minimum proportion of a security’s shares that must be freely tradable (not closely held) in the market.
-
D.
freedBy
Indicates that an entity is released or liberated as a result of an action performed by another entity.
-
E.
equalityCondition
Indicates that two values, expressions, or attributes must be exactly the same for the condition to be satisfied.
- F. None of above. chosen
Provenance (4 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_69ca83d9844081908e561e367fda6d45 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc96b650648190a8f59cee402d12aa |
completed | April 1, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc6a3c78388190a7436acc0e44ff55 |
completed | April 1, 2026, 12:43 a.m. |
Created at: March 30, 2026, 7:14 p.m.