Triple
T30077680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Powers |
E764365
|
entity |
| Predicate | hasOriginalArticle |
P168550
|
FINISHED |
| Object | "le" in "le Poer" |
—
|
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: "le" in "le Poer" | Statement: [Powers, hasOriginalArticle, "le" in "le Poer"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalArticle Context triple: [Powers, hasOriginalArticle, "le" in "le Poer"]
-
A.
hasOriginalStory
Indicates that one entity serves as the original narrative source or story upon which the other entity is based or derived.
-
B.
hasOriginalPaperTitle
chosen
Indicates that an entity (such as a publication or work) is associated with the title it originally had when first created or published.
-
C.
hasOriginalVersion
Indicates that one entity is the original or initial version from which another entity is derived or adapted.
-
D.
hasOriginalWorkSetting
Indicates that an entity is associated with the setting or context in which the original work or source material takes place.
-
E.
hasOriginalWorkMedium
Indicates that an original creative work is associated with a specific medium or material in which it was first produced.
- 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 29, 2026, 7:02 p.m.