Triple
T22527052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | أفواه وأرانب |
E556933
|
entity |
| Predicate | عنوانه يرمز إلى |
P30784
|
FINISHED |
| Object | كثرة الأفواه وقلة الموارد |
—
|
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: كثرة الأفواه وقلة الموارد | Statement: [أفواه وأرانب, عنوانه يرمز إلى, كثرة الأفواه وقلة الموارد]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: عنوانه يرمز إلى Context triple: [أفواه وأرانب, عنوانه يرمز إلى, كثرة الأفواه وقلة الموارد]
-
A.
titleMeaning
Indicates that one entity expresses or explains the meaning, significance, or interpretation of another entity’s title.
-
B.
titleAlludesTo
Indicates that one title makes an indirect or suggestive reference to the content, theme, or another work associated with the other.
-
C.
titleRepresents
chosen
Indicates that a given title stands for, denotes, or symbolizes a particular concept, role, work, or entity.
-
D.
hasTitlePhraseReferringTo
Indicates that an entity’s title includes or is associated with a specific phrase that refers to another entity or concept.
-
E.
refersToTitleHolder
Indicates that one entity makes reference to, or designates, the entity that currently holds a specific title or position.
- 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_69e11e57483c8190b0887c4f8ff26446 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ed411488190a51320930b9805c2 |
completed | April 29, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69e898c864148190a3f5feec7967d49c |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:51 p.m.