Triple
T16789634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ibn Mūsā |
E408071
|
entity |
| Predicate | morphologicalComponents |
P31789
|
FINISHED |
| Object | ibn |
—
|
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: ibn | Statement: [ibn Mūsā, morphologicalComponents, ibn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: morphologicalComponents Context triple: [ibn Mūsā, morphologicalComponents, ibn]
-
A.
morphologicalComparison
Indicates a relationship where two or more entities are compared based on differences or similarities in their morphological (form or structural) characteristics.
-
B.
relatedMorphologicalFeature
chosen
Indicates that one entity is connected to another through a shared or corresponding morphological feature or structure.
-
C.
morphologicalDiversity
Indicates variation in the forms, structures, or shapes of entities within a group or system.
-
D.
dimensionOfComponents
Indicates that a specified dimension value is associated with, or applies to, the components of an object or system.
-
E.
morphologicalRelation
Indicates a relationship between linguistic forms where one word or morpheme is derived from, inflected from, or otherwise morphologically related to another.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2a50e18819090a30e1f38e520e0 |
completed | April 18, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.