Triple
T4360028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicomedes I of Bithynia |
E98639
|
entity |
| Predicate | invited |
P25673
|
FINISHED |
| Object | Galatian Celts into Asia Minor |
—
|
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: Galatian Celts into Asia Minor | Statement: [Nicomedes I of Bithynia, invited, Galatian Celts into Asia Minor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invited Context triple: [Nicomedes I of Bithynia, invited, Galatian Celts into Asia Minor]
-
A.
invitesParticipationOf
chosen
Indicates that one entity actively requests or encourages another entity to take part in an activity, event, or process.
-
B.
isInvited
Indicates that one entity has extended an invitation to another entity to participate in or attend something.
-
C.
invitationAuthority
Indicates that one entity has the authority or permission to invite another entity (or others) to participate in an event, group, or activity.
-
D.
invitesResponseOf
Indicates that one entity’s action, message, or state prompts, elicits, or calls for a response from another entity.
-
E.
acceptedIn
Indicates that something has been formally received, approved, or admitted into a particular context, group, or system.
- 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351e3220881909dc9d02ab024abf5 |
completed | March 12, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:16 p.m.