Triple
T24980498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Splackavellie |
E625148
|
entity |
| Predicate | hasSecretLoverTheme |
P115400
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Splackavellie, hasSecretLoverTheme, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecretLoverTheme Context triple: [Splackavellie, hasSecretLoverTheme, true]
-
A.
secretlyIs
Indicates that one entity possesses a hidden or undisclosed identity, role, or attribute in relation to another entity.
-
B.
hasFamilySecret
Indicates that there exists a confidential or hidden matter shared within or pertaining to a family relationship.
-
C.
hasSecretMarriageWith
Indicates a relationship where two entities are secretly married to each other, with the marriage intentionally concealed from others.
-
D.
rumoredLoverOf
chosen
Indicates that one entity is widely believed or speculated to be the romantic partner or lover of another entity, without confirmed evidence.
-
E.
hasConcubineType
Indicates that an entity has or is associated with a concubine of a specified type or classification.
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 18, 2026, 6:02 a.m.