Triple
T24058338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theseus and the Amazons |
E595871
|
entity |
| Predicate | hasGroupCharacter |
P47706
|
FINISHED |
| Object | Amazons |
—
|
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: Amazons | Statement: [Theseus and the Amazons, hasGroupCharacter, Amazons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGroupCharacter Context triple: [Theseus and the Amazons, hasGroupCharacter, Amazons]
-
A.
hasCharacterGroupName
Indicates that an entity is associated with a specific name identifying a group of characters.
-
B.
hasCharacterClass
Indicates that an entity (such as a character) belongs to or is assigned a particular character class or role type.
-
C.
hasNotableGroupCharacteristic
Indicates that a group possesses a distinctive or noteworthy characteristic that sets it apart from other groups.
-
D.
hasGuardCharacter
Indicates that one entity serves as a guard or protective character for another entity.
-
E.
associatedWithCharacterGroup
chosen
Indicates that an entity has a connection or affiliation with a particular group of characters.
- 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_69e288c184b081909f1f1751fb8e299a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1da52b9d48190b503fad5ff70e4c6 |
completed | April 29, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:36 p.m.