Triple
T8827382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fortunato |
E210048
|
entity |
| Predicate | relationshipToMontresor |
P84855
|
FINISHED |
| Object | acquaintance |
—
|
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: acquaintance | Statement: [Fortunato, relationshipToMontresor, acquaintance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToMontresor Context triple: [Fortunato, relationshipToMontresor, acquaintance]
-
A.
relationshipToHillHouse
Indicates the type or nature of a subject’s relationship or connection to Hill House.
-
B.
relationshipWithMiladyDeWinter
Indicates a personal or interpersonal connection that an entity has with Milady de Winter, such as familial, romantic, adversarial, or other significant relational ties.
-
C.
hasRelationshipToJackTorrance
Indicates that one entity has some form of relationship or connection to Jack Torrance.
-
D.
relationshipToHesterPrynne
Indicates the specific familial, social, or emotional connection that an entity has to Hester Prynne.
-
E.
relationshipToManfred
Indicates the specific type of relationship or connection that one entity has to the individual named Manfred.
- F. None of above. chosen
Provenance (4 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_69ca8365b28081909e48e45e95dfc405 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc6034e8dc819099116d772e87569a |
completed | April 1, 2026, midnight |
| PD | Predicate disambiguation | batch_69cc5c23d08481908d8c9b0ad3d1dc00 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:47 p.m.