Triple
T34666417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potemkin village |
E890268
|
entity |
| Predicate | allegedlyCreatedFor |
P7551
|
FINISHED |
| Object | Catherine the Great |
—
|
NE NERFINISHED |
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: Catherine the Great | Statement: [Potemkin village, allegedlyCreatedFor, Catherine the Great]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedlyCreatedFor Context triple: [Potemkin village, allegedlyCreatedFor, Catherine the Great]
-
A.
isFictionallyCreatedBy
Indicates that an entity is a fictional creation authored, invented, or brought into existence within a narrative by another entity.
-
B.
createdFor
chosen
Indicates that one entity was made, produced, or designed specifically to serve, benefit, or be used by another entity.
-
C.
allegedUse
Indicates that something is claimed or suspected to have been used, without confirming that the use actually occurred.
-
D.
allegedFounderInStory
Indicates that an entity is claimed or reported, within a particular narrative or account, to be the founder of something.
-
E.
createdForWorkBy
Indicates that something was created specifically for use in work or professional activities by a particular agent or person.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 1, 2026, 2:04 a.m.