Triple
T26897401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Hans |
E677931
|
entity |
| Predicate | pretendsTo |
P84851
|
FINISHED |
| Object | fall in love with Anna |
—
|
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: fall in love with Anna | Statement: [Prince Hans, pretendsTo, fall in love with Anna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pretendsTo Context triple: [Prince Hans, pretendsTo, fall in love with Anna]
-
A.
pretendsConcernFor
chosen
Indicates that one entity feigns or simulates concern for another entity or situation without genuinely feeling it.
-
B.
emulates
Indicates that one entity imitates or reproduces the behavior, function, or characteristics of another.
-
C.
disguisedAs
Indicates that one entity is intentionally presenting itself as, or made to appear as, another entity in order to conceal its true identity.
-
D.
pretenderPeriod
Indicates a time span during which an entity falsely claims or is regarded as holding a role, title, or status it does not legitimately possess.
-
E.
actsInSteadOf
Indicates that one entity performs an action or fulfills a role as a substitute or proxy for 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61fac4c808190a27f121fac4fe61c |
completed | May 2, 2026, 4 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:48 a.m.