Triple
T19488992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nick |
E487595
|
entity |
| Predicate | hasFirstNameOnly |
P136108
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Nick, hasFirstNameOnly, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstNameOnly Context triple: [Nick, hasFirstNameOnly, true]
-
A.
hasInitialOnlySurname
Indicates that a person is represented by only the initial of their given name together with their full surname, rather than their complete given name.
-
B.
hasFirstNameFromParent
Indicates that an entity’s first name is derived from or inherited from one of its parents’ names.
-
C.
hasNoPersonalNameIn
Indicates that an entity lacks a specific personal name within a given context, language, or naming system.
-
D.
hasSurnamePrefix
Indicates that one entity’s surname begins with, or is prefixed by, the string or component specified by the other entity.
-
E.
hasGivenNameCombination
Indicates that an entity is associated with a specific combination or sequence of given (first) names.
- F. None of above. chosen
Provenance (4 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6348ad4088190b530f47efca90165 |
completed | April 20, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004d3a708190a1c13c8f644f3926 |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:39 p.m.