Triple
T24815094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuroda Nagamasa |
E620896
|
entity |
| Predicate | movedToDomain |
P79166
|
FINISHED |
| Object | Chikuzen Province |
—
|
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: Chikuzen Province | Statement: [Kuroda Nagamasa, movedToDomain, Chikuzen Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movedToDomain Context triple: [Kuroda Nagamasa, movedToDomain, Chikuzen Province]
-
A.
movedFor
Indicates that one entity changed its location or position for the benefit, purpose, or in response to another entity.
-
B.
formerDomain
chosen
Indicates that one entity was previously the domain or area of control, influence, or ownership of another entity, but no longer is.
-
C.
movedOn
Indicates that an entity changed its position or location from one place to another at some point in time.
-
D.
replacedInDomain
Indicates that one entity has been superseded or substituted by another within a specific domain or contextual scope.
-
E.
movedPremises
Indicates that an entity has changed its location or base of operations from one set of premises to another.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:02 a.m.