Triple
T25289896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mansur |
E634050
|
entity |
| Predicate | oftenCombinedIn |
P70673
|
FINISHED |
| Object | compound Arabic names |
—
|
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: compound Arabic names | Statement: [Mansur, oftenCombinedIn, compound Arabic names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenCombinedIn Context triple: [Mansur, oftenCombinedIn, compound Arabic names]
-
A.
combinedIn
chosen
Indicates that two or more entities are merged, joined, or used together to form a single combined whole or context.
-
B.
actedTogetherWith
Indicates that two entities participated in the same performance or production, collaborating or appearing together in an acting context.
-
C.
endedUnionBetween
Indicates that one entity caused or marked the termination of a union, alliance, or partnership with another entity.
-
D.
formedTogetherWith
Indicates that two or more entities were created, established, or brought into existence at the same time or as part of the same formation process.
-
E.
oftenAccompaniedBy
Indicates that one entity is frequently found together with, occurs alongside, or is commonly associated in presence or use with 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48e0c2aa88190aca9e47be7138854 |
completed | May 1, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:21 p.m.