Triple
T19999700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honey |
E494283
|
entity |
| Predicate | hasRelationshipTypeWithNick |
P10690
|
FINISHED |
| Object | wife |
—
|
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: wife | Statement: [Honey, hasRelationshipTypeWithNick, wife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelationshipTypeWithNick Context triple: [Honey, hasRelationshipTypeWithNick, wife]
-
A.
hasNicknamedEntityType
Indicates that an entity is associated with another entity type specifically in the role of being its nickname or informal name.
-
B.
hasSymbolicRelationshipType
Indicates that there exists a symbolic (non-literal) relationship of a specified type between two entities.
-
C.
hasNicknameStatus
Indicates that an entity holds a particular status or classification specifically related to its nickname.
-
D.
hasCentralRelationshipType
Indicates that there exists a primary or most significant type of relationship that characterizes how two entities are related to each other.
-
E.
relationshipType
chosen
Indicates the specific kind of relationship that exists between two or more entities.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a09bdc819083305b08a11c6e34 |
completed | April 20, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:32 p.m.