Triple
T38067586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Βάτεια |
E950512
|
entity |
| Predicate | maritalConnectionSignificance |
P37708
|
FINISHED |
| Object | link to Trojan royal line |
—
|
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: link to Trojan royal line | Statement: [Βάτεια, maritalConnectionSignificance, link to Trojan royal line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritalConnectionSignificance Context triple: [Βάτεια, maritalConnectionSignificance, link to Trojan royal line]
-
A.
marriageSignificance
chosen
Indicates the importance, impact, or meaningfulness that a marriage holds within a given context or for the entities involved.
-
B.
maritalRelations
Indicates a legally or socially recognized spousal relationship or marriage-based connection between two entities.
-
C.
regardsMarriageAs
Indicates that one entity holds a particular view, attitude, or evaluative stance toward the institution or concept of marriage.
-
D.
characterRelativeByMarriage
Indicates that one character is related to another through marriage rather than by blood.
-
E.
hasMaritalFunction
Indicates that one entity serves a role or performs a function within the context of a marital relationship or institution.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.