Triple
T30511683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estella |
E776442
|
entity |
| Predicate | relationshipWithPip |
P204043
|
FINISHED |
| Object | unrequited love from Pip |
—
|
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: unrequited love from Pip | Statement: [Estella, relationshipWithPip, unrequited love from Pip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipWithPip Context triple: [Estella, relationshipWithPip, unrequited love from Pip]
-
A.
relationshipToPlayer
Indicates the type of personal or social connection an entity has with the player.
-
B.
relationshipToPoro
Indicates the type or nature of a relationship that an entity has to a Poro.
-
C.
relationToBPP
Indicates the specific type of relationship or association an entity has to a designated BPP (e.g., as owner, member, participant, or related party).
-
D.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
-
E.
relationshipToPete
Indicates the specific type of relationship or connection that an entity has to Pete.
- 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_69f2249a155c8190b1d512106007e9bb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0311c202408190be88a85337aacf11 |
completed | May 12, 2026, 11:40 a.m. |
| PD | Predicate disambiguation | batch_6a0310b0c9c88190ab218d47d4f432ed |
completed | May 12, 2026, 11:36 a.m. |
| PDg | Predicate description generation | batch_6a0311c145a08190ba7658db898ab7d6 |
completed | May 12, 2026, 11:40 a.m. |
Created at: April 29, 2026, 8:16 p.m.