Triple
T11575571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Wall |
E274494
|
entity |
| Predicate | nameIsRecordedAs |
P744
|
FINISHED |
| Object | bearer of the surname "Wall" |
—
|
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: bearer of the surname "Wall" | Statement: [Frank Wall, nameIsRecordedAs, bearer of the surname "Wall"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameIsRecordedAs Context triple: [Frank Wall, nameIsRecordedAs, bearer of the surname "Wall"]
-
A.
hasNameGivenTo
Indicates that one entity is the name that has been assigned or given to another entity.
-
B.
transcribedName
Indicates that one entity is a written or phonetic rendering of another entity’s name, typically adapted to a different script, language, or transcription system.
-
C.
realName
Indicates that one entity is the actual, full, or birth name of another entity, which may be known by an alias, nickname, or alternate identity.
-
D.
nameOf
chosen
Indicates that one entity is the name or designation of another entity.
-
E.
namesakeStatus
Indicates that one entity serves as the namesake of another, or that two entities share a relationship based on having the same name.
- 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d89049721081909278adfada668ef9 |
completed | April 10, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69d85dcbacd0819094d4a1237055affa |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.