Triple
T4702073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abdus |
E104296
|
entity |
| Predicate | nameElementPosition |
P1082
|
FINISHED |
| Object | prefix in compound theophoric 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: prefix in compound theophoric names | Statement: [Abdus, nameElementPosition, prefix in compound theophoric names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameElementPosition Context triple: [Abdus, nameElementPosition, prefix in compound theophoric names]
-
A.
nameElement
Indicates that one entity serves as the name or label assigned to another entity or element.
-
B.
namePosition
chosen
Indicates the positional or ordering relationship of a name within a sequence or structured context (e.g., first, last, or specific index).
-
C.
nameElementIn
Indicates that an entity is (or contains) a specific name element within a larger naming structure or system.
-
D.
nameElements
Indicates that an entity assigns or specifies the names of multiple elements within a set or structure.
-
E.
namedAfterPosition
Indicates that an entity is named after a specific position, role, or rank associated with it.
- 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_69bd43e9b88481908582103dcadff3d9 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650ad0f88190844bfcb46b3071c2 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd621ba7448190a53ab1e2897acf71 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:17 p.m.