Triple
T3306924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabine women |
E69472
|
entity |
| Predicate | familyRelationInMyth |
P9987
|
FINISHED |
| Object | daughters of Sabine families |
—
|
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: daughters of Sabine families | Statement: [Sabine women, familyRelationInMyth, daughters of Sabine families]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyRelationInMyth Context triple: [Sabine women, familyRelationInMyth, daughters of Sabine families]
-
A.
fictionalRelationship
Indicates a relationship that exists only within a fictional or imagined context between entities.
-
B.
relationshipToCharacter
Indicates the specific type of personal, social, or narrative connection that one entity has to a given character.
-
C.
historicalRelationship
Indicates a relationship that existed between entities in the past, often tied to a specific historical period, context, or event.
-
D.
linkedToMythology
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
-
E.
mythologicalRole
chosen
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
- 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_69ad859f218081909458d2cebbf57565 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0caa0988190872fc7648e64571f |
completed | March 8, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.