Triple
T30282735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sergeant Arthur Wilson |
E770144
|
entity |
| Predicate | impliedRelationshipType |
P43530
|
FINISHED |
| Object | possible father of Frank Pike |
—
|
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: possible father of Frank Pike | Statement: [Sergeant Arthur Wilson, impliedRelationshipType, possible father of Frank Pike]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impliedRelationshipType Context triple: [Sergeant Arthur Wilson, impliedRelationshipType, possible father of Frank Pike]
-
A.
relationshipType
Indicates the specific kind of relationship that exists between two or more entities.
-
B.
referralRelationship
Indicates a relationship in which one entity directs or recommends another entity to a third party for services, information, or further action.
-
C.
relatedType
chosen
Indicates that one entity is connected to another through a specified type or category of relationship.
-
D.
relationshipTypeStart
Indicates the type or category of relationship that begins or is initiated at a specific point or event.
-
E.
identityRelation
Indicates that two entities are in fact the very same entity, not merely similar or equivalent.
- 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_69f224868fa8819099127eaf8855a28f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68106a8ac8190ab775d61ae360c56 |
completed | May 2, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:45 p.m.