Triple
T8447622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Themyscira |
E199714
|
entity |
| Predicate | roleInLore |
P42552
|
FINISHED |
| Object | homeland of the Amazons |
—
|
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: homeland of the Amazons | Statement: [Themyscira, roleInLore, homeland of the Amazons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInLore Context triple: [Themyscira, roleInLore, homeland of the Amazons]
-
A.
roleInStories
chosen
Indicates the specific function, position, or character part an entity plays within one or more stories.
-
B.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
C.
roleInWZRD
Indicates that an entity holds a specific role or function within the context of WZRD.
-
D.
roleInTheory
Indicates the specific function, position, or contribution that an entity has within a particular theory or theoretical framework.
-
E.
roleInRhyme
Indicates the specific function or part an entity plays within a rhyme, such as a character, object, or structural element of the rhyming text.
- 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_69ca83170f9081909cd98f55614c6476 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe44480ec8190b32443a53cd4f943 |
completed | March 31, 2026, 3:12 p.m. |
| PD | Predicate disambiguation | batch_69cbd0f5a3648190beb53a139a2d5482 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:09 p.m.