Triple
T18263885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Foster |
E437432
|
entity |
| Predicate | relationshipTypeWithLeninaCrowne |
P10690
|
FINISHED |
| Object | casual |
—
|
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: casual | Statement: [Henry Foster, relationshipTypeWithLeninaCrowne, casual]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipTypeWithLeninaCrowne Context triple: [Henry Foster, relationshipTypeWithLeninaCrowne, casual]
-
A.
relationshipType
chosen
Indicates the specific kind of relationship that exists between two or more entities.
-
B.
relationTypeToHenryVIII
Indicates the specific type of relationship an entity has to Henry VIII (e.g., familial, political, or social connection).
-
C.
titleRelation
Indicates a relationship where one entity serves as the title, designation, or formal name associated with another entity.
-
D.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
-
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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ff78b188819081da8e1d389c6c79 |
completed | April 19, 2026, 4:14 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.