Triple
T29261743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Burnusi |
E741862
|
entity |
| Predicate | refersToAssociationWith |
P114713
|
FINISHED |
| Object | burnus cloak |
—
|
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: burnus cloak | Statement: [al-Burnusi, refersToAssociationWith, burnus cloak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToAssociationWith Context triple: [al-Burnusi, refersToAssociationWith, burnus cloak]
-
A.
associatedWithAssociation
Indicates a relationship where an entity is linked or connected to a particular association or organization.
-
B.
refersToGroupAssociatedWith
chosen
Indicates that one entity makes reference to a group that is associated or linked with another specified entity.
-
C.
endedAssociationWith
Indicates that a previously existing association or relationship between two entities has been terminated or discontinued.
-
D.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
E.
supportsAssociationWith
Indicates that one entity provides backing, endorsement, or assistance for an association or relationship involving 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 28, 2026, 12:42 p.m.