Triple
T35025829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moresnet |
E1010333
|
entity |
| Predicate | proposedNewName |
P122448
|
FINISHED |
| Object | Amikejo |
—
|
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: Amikejo | Statement: [Moresnet, proposedNewName, Amikejo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedNewName Context triple: [Moresnet, proposedNewName, Amikejo]
-
A.
nameProposedIn
chosen
Indicates that a particular name was suggested or put forward within a specific proposal, context, or event.
-
B.
proposedStateName
Indicates that one entity has suggested or put forward a particular name to be used as the state name for another entity.
-
C.
nameProposedBy
Indicates that one entity is the proposer or originator of a particular name assigned to another entity.
-
D.
adoptedNewNameDueTo
Indicates that an entity changed its original name to a new one as a result of, or in response to, another specified entity or circumstance.
-
E.
changedNameBy
Indicates that one entity altered or updated the name of 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_69f76dccf0108190af43b465d3750196 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:01 p.m.