Triple
T2586029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Kirk |
E58005
|
entity |
| Predicate | hasNameStructure |
P28784
|
FINISHED |
| Object | forename followed by surname |
—
|
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: forename followed by surname | Statement: [John Kirk, hasNameStructure, forename followed by surname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameStructure Context triple: [John Kirk, hasNameStructure, forename followed by surname]
-
A.
namingStructure
Indicates a relationship where one entity defines, organizes, or constrains the naming or label format used for another entity.
-
B.
hasProperName
Indicates that an entity is associated with a specific proper name used to uniquely identify it.
-
C.
hasStructureType
Indicates that an entity possesses or is classified by a specific structural type or configuration.
-
D.
hasNameOrder
chosen
Indicates the specific sequence or arrangement in which the components of a name (e.g., given name, family name, titles) are ordered.
-
E.
hasGivenNameBasis
Indicates that one entity’s given name is derived from, based on, or formed using another entity (such as a name, word, or person) as its basis.
- 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_69ab4ac019c8819094add11c46706e32 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd3f6f6ac8190abff7b8b6ff3c023 |
completed | March 7, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69abd0d19308819089ee942513d567a4 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.