Triple
T173549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Hancock |
E3527
|
entity |
| Predicate | nameGivesRiseTo |
P6111
|
FINISHED |
| Object | “John Hancock” as a synonym for “signature” in American English |
—
|
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: “John Hancock” as a synonym for “signature” in American English | Statement: [John Hancock, nameGivesRiseTo, “John Hancock” as a synonym for “signature” in American English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameGivesRiseTo Context triple: [John Hancock, nameGivesRiseTo, “John Hancock” as a synonym for “signature” in American English]
-
A.
nameOf
Indicates that one entity is the name or designation of another entity.
-
B.
eraName
Indicates the named historical or chronological era associated with an entity or time period.
-
C.
givenName
Indicates the personal first name assigned to an individual.
-
D.
hasNameOrigin
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
E.
namedAfter
Indicates that one entity has been given its name in honor of, or derived from, another entity.
- 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a258e1ec008190a89dd452f72574f4 |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a256689f908190afeb5ee82022a911 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a25737f9188190b9690dce98aed83a |
completed | Feb. 28, 2026, 2:47 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.