Triple
T26897413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Hans |
E677931
|
entity |
| Predicate | sentBackTo |
P46979
|
FINISHED |
| Object | Southern Isles |
—
|
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: Southern Isles | Statement: [Prince Hans, sentBackTo, Southern Isles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sentBackTo Context triple: [Prince Hans, sentBackTo, Southern Isles]
-
A.
sentAs
Indicates that one entity was transmitted, dispatched, or delivered in the form, role, or capacity of another (e.g., an item or message being sent as something specific).
-
B.
sentAfter
Indicates that one message or item was sent at a later time than another specified message or item.
-
C.
sentAgainst
Indicates that something (such as a message, request, or action) is directed or dispatched in opposition to a particular target or entity.
-
D.
sentAwayBy
Indicates that one entity was made to leave or be dismissed from a place or situation by another entity.
-
E.
wasReturnedTo
chosen
Indicates that an entity was sent or brought back to a previous owner, location, or state after having been away or removed.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61fac4c808190a27f121fac4fe61c |
completed | May 2, 2026, 4 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:48 a.m.