Triple
T28082615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anne Whittle |
E709725
|
entity |
| Predicate | allegedFamiliar |
P120587
|
FINISHED |
| Object | a spirit called Fancie |
—
|
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: a spirit called Fancie | Statement: [Anne Whittle, allegedFamiliar, a spirit called Fancie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedFamiliar Context triple: [Anne Whittle, allegedFamiliar, a spirit called Fancie]
-
A.
allegedImpostor
Indicates that one entity is claimed or suspected to be fraudulently posing as another entity.
-
B.
allegedAgentOf
Indicates that one entity is claimed or suspected, but not confirmed, to be the agent responsible for an action or event involving another entity.
-
C.
hasAllegedRelationshipWith
chosen
Indicates a claimed or suspected relationship between two entities that is not confirmed as factual.
-
D.
allegedCompanions
Indicates that two or more entities are claimed or reported to have been companions or associates, without confirming the truth of that relationship.
-
E.
allegedAncestor
Indicates that one entity is claimed or suspected to be an ancestor of another, without confirming that the ancestral relationship is true.
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 8:53 p.m.