Triple
T35573271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bithynians |
E1028001
|
entity |
| Predicate | becameClientStateOf |
P45767
|
FINISHED |
| Object | Roman Republic |
—
|
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: Roman Republic | Statement: [Bithynians, becameClientStateOf, Roman Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameClientStateOf Context triple: [Bithynians, becameClientStateOf, Roman Republic]
-
A.
wasClientStateOf
chosen
Indicates that one entity functioned as a client state under the political, economic, or military influence or control of another entity.
-
B.
becameStateOf
Indicates that an entity transitioned into and assumed the status, condition, or role defined by a particular state.
-
C.
movedToState
Indicates that an entity changed its location or status from one state to another specified state.
-
D.
transitionState
Indicates a change in condition or phase from one defined state to another within a process or system.
-
E.
hadStateFrom
Indicates that an entity possessed or was in a particular state starting from a specified point in time.
- 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_69f76e0386688190b931bacdc145938c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.