Triple
T23316516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jordan, son of Frederick II |
E590721
|
entity |
| Predicate | relativeTypeToAgnes |
P138295
|
FINISHED |
| Object | younger half-brother |
—
|
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: younger half-brother | Statement: [Jordan, son of Frederick II, relativeTypeToAgnes, younger half-brother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeTypeToAgnes Context triple: [Jordan, son of Frederick II, relativeTypeToAgnes, younger half-brother]
-
A.
relationshipToAgnes
chosen
Indicates the specific familial, social, or other relational connection that one entity has to the person named Agnes.
-
B.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
C.
relationshipType
Indicates the specific kind of relationship that exists between two or more entities.
-
D.
allyRelation
Indicates a cooperative, supportive relationship in which the entities act as allies toward shared or aligned goals.
-
E.
relationshipTypeWithSassi
Indicates the specific type or nature of the relationship that an entity has with Sassi.
- 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197816024819086c547ba89f84286 |
completed | April 29, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:06 p.m.