Triple
T13733971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naeem |
E329885
|
entity |
| Predicate | hasNameComponentRelationTo |
P90387
|
FINISHED |
| Object | i |
—
|
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: i | Statement: [Naeem, hasNameComponentRelationTo, i]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameComponentRelationTo Context triple: [Naeem, hasNameComponentRelationTo, i]
-
A.
isRelatedName
Indicates that one name is connected to another through a variant, derivative, or otherwise non-identical but related naming relationship.
-
B.
isComponentOfNameOf
chosen
Indicates that one entity is the name of a component or part belonging to another entity.
-
C.
hasNameDayRelation
Indicates a relationship where a person’s name is associated with a specific name day or feast day in a calendar.
-
D.
hasComponentSurname
Indicates that an entity’s full name includes a specified surname as one of its component parts.
-
E.
hasNameInFamily
Indicates that an entity is known or referred to by a particular name within the context of a specific family or familial group.
- 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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de0201d3c48190aa306be231a28bc1 |
completed | April 14, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:55 p.m.