Triple
T28113945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loftus |
E710566
|
entity |
| Predicate | hasNameComponentIn |
P24447
|
FINISHED |
| Object | Robert Loftus Owen Versfeld |
—
|
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: Robert Loftus Owen Versfeld | Statement: [Loftus, hasNameComponentIn, Robert Loftus Owen Versfeld]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameComponentIn Context triple: [Loftus, hasNameComponentIn, Robert Loftus Owen Versfeld]
-
A.
hasComponentGivenName
Indicates that an entity includes a component whose specific given (first) name is the value of the predicate.
-
B.
hasComponentName
chosen
Indicates that an entity includes or is associated with a component identified by a specific name.
-
C.
isComponentOfNameOf
Indicates that one entity is the name of a component or part belonging to another entity.
-
D.
hasComponentSurname
Indicates that an entity’s full name includes a specified surname as one of its component parts.
-
E.
hasNameInFamily
Indicates that an entity is known or referred to by a particular name within the context of a specific family or familial group.
- 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_69ef9b72f63081909dfbc2c1ddae86c6 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: April 27, 2026, 9:13 p.m.