Triple
T30616138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawk and Dove |
E779320
|
entity |
| Predicate | originalRelationship |
P202137
|
FINISHED |
| Object | brothers |
—
|
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: brothers | Statement: [Hawk and Dove, originalRelationship, brothers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalRelationship Context triple: [Hawk and Dove, originalRelationship, brothers]
-
A.
coversRelationship
Indicates that one entity extends over, includes, or provides encompassing coverage for another entity or set of entities.
-
B.
laterRelationshipWith
Indicates that one entity has a relationship with another that occurs at a later time relative to some reference point or prior relationship.
-
C.
subjectRelation
Indicates that one entity stands in a specified relational role or connection to another entity.
-
D.
allyRelation
Indicates a cooperative, supportive relationship in which the entities act as allies toward shared or aligned goals.
-
E.
basisOfRelationship
Indicates that one entity serves as the foundational reason, cause, or justification for the relationship that exists between two or more entities.
- F. None of above. chosen
Provenance (4 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0058c341ac8190825067dc25158839 |
completed | May 10, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_6a005857249c81908b27587b84d84dbb |
completed | May 10, 2026, 10:05 a.m. |
| PDg | Predicate description generation | batch_6a0058c26638819085d8cbaa0bd4ccf0 |
completed | May 10, 2026, 10:06 a.m. |
Created at: April 29, 2026, 8:26 p.m.