Triple
T19646341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zayn |
E471680
|
entity |
| Predicate | derivedFromRoot |
P909
|
FINISHED |
| Object | Arabic root ز ي ن (z-y-n) |
—
|
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: Arabic root ز ي ن (z-y-n) | Statement: [Zayn, derivedFromRoot, Arabic root ز ي ن (z-y-n)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derivedFromRoot Context triple: [Zayn, derivedFromRoot, Arabic root ز ي ن (z-y-n)]
-
A.
derivedFrom
chosen
Indicates that one entity originates, is obtained, or is developed from another source entity.
-
B.
derivedBy
Indicates that one entity is obtained, produced, or inferred from another through some transformation, process, or reasoning.
-
C.
inheritedFrom
Indicates that one entity has received or derived something (such as traits, rights, or property) from another entity, typically a predecessor or ancestor.
-
D.
developedFrom
Indicates that one entity originates, evolves, or is derived from another as its source or precursor.
-
E.
isRootOf
Indicates that one entity is the root or origin point from which another entity directly or indirectly descends or is derived.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641250e108190a707452fefc87041 |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.