Triple
T30709049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lindsay |
E781838
|
entity |
| Predicate | hasNotableBearerSurname |
P202111
|
FINISHED |
| Object | Norman Lindsay |
—
|
NE NERFINISHED |
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: Norman Lindsay | Statement: [Lindsay, hasNotableBearerSurname, Norman Lindsay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableBearerSurname Context triple: [Lindsay, hasNotableBearerSurname, Norman Lindsay]
-
A.
hasSurnameBearer
Indicates that a particular surname is borne or carried by a specific person or entity.
-
B.
hasNotableSurname
Indicates that an entity bears a surname that is recognized as notable, distinguished, or of particular significance.
-
C.
hasNotableBearerFamily
Indicates that a family is recognized for having at least one notable or distinguished member associated with it.
-
D.
hasNotableBearerTitle
Indicates that an entity is associated with a notable person or group who holds a specific title or designation.
-
E.
hasBaseSurname
Indicates that an entity’s surname is derived from, or fundamentally corresponds to, a specified base or canonical surname.
- 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_69f224abfcf081909492e64d3cc35262 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a005247dba08190acadf962bcefe4a0 |
completed | May 10, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_6a00519029848190a234358dfba45084 |
completed | May 10, 2026, 9:36 a.m. |
| PDg | Predicate description generation | batch_6a00524723408190b0294e87e5cf7715 |
completed | May 10, 2026, 9:39 a.m. |
Created at: April 29, 2026, 8:35 p.m.