Triple
T30511678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estella |
E776442
|
entity |
| Predicate | objectOf |
P110638
|
FINISHED |
| Object | Pip’s obsessive love |
—
|
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: Pip’s obsessive love | Statement: [Estella, objectOf, Pip’s obsessive love]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: objectOf Context triple: [Estella, objectOf, Pip’s obsessive love]
-
A.
objectOfVerb
Indicates that one entity serves as the direct object or recipient of the action expressed by a given verb in a clause.
-
B.
notableObject
Indicates that an entity is especially significant, famous, or noteworthy as an object in a given context or domain.
-
C.
typicalObjectType
Indicates that something is a common or characteristic type of object typically associated with or involved in another entity or situation.
-
D.
linkedToObject
Indicates that one entity is connected or associated with another entity in some meaningful way.
-
E.
objet
chosen
Indicates that one entity is the object (recipient or target) of an action or relation performed by another entity.
- 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_69f2249a155c8190b1d512106007e9bb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:16 p.m.