Triple
T7001661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helvetii |
E162350
|
entity |
| Predicate | forcedToReturnTo |
P73520
|
FINISHED |
| Object | their homeland in the Swiss Plateau |
—
|
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: their homeland in the Swiss Plateau | Statement: [Helvetii, forcedToReturnTo, their homeland in the Swiss Plateau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forcedToReturnTo Context triple: [Helvetii, forcedToReturnTo, their homeland in the Swiss Plateau]
-
A.
returnedFrom
Indicates that an entity has come back or been sent back from a specified source, location, or prior state.
-
B.
returnsTo
Indicates that an entity goes back to a previous location, state, or entity it was associated with before.
-
C.
wasReturnedTo
Indicates that an entity was sent or brought back to a previous owner, location, or state after having been away or removed.
-
D.
returnedVia
Indicates that something was sent back or responded to through a specified medium, channel, or method.
-
E.
forcedBy
Indicates that an entity is compelled or coerced into an action or state by another entity.
- 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_69c68857ffc08190857dc62cd5253777 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc0f8830819091f4356296234713 |
completed | March 27, 2026, 7:35 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c67c94819084fdcf0398606027 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c575f081908b43d95d1d99b1a4 |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:33 p.m.