Triple
T4678992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hernici |
E103750
|
entity |
| Predicate | lossOfIndependence |
P34533
|
FINISHED |
| Object | 4th century BC |
—
|
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: 4th century BC | Statement: [Hernici, lossOfIndependence, 4th century BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lossOfIndependence Context triple: [Hernici, lossOfIndependence, 4th century BC]
-
A.
lostSovereigntyIn
Indicates that an entity ceased to possess or exercise sovereign authority within a specified place or domain.
-
B.
independenceRestored
Indicates that a previously dependent or controlled entity has regained its autonomy or self-governance.
-
C.
independenceFrom
Indicates that one entity is not controlled, governed, or significantly influenced by another entity.
-
D.
endOfIndependence
chosen
Indicates the point or event at which an entity’s prior state of independence comes to an end, typically due to loss of autonomy or incorporation into another entity.
-
E.
gainedIndependenceAs
Indicates that an entity achieved political or administrative independence in the specific form, status, or identity denoted by another entity.
- 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_69bd43dda32c8190938b37744ca270fc |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6217e0088190836570522e324dc6 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:16 p.m.