Triple
T23957874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onua |
E603845
|
entity |
| Predicate | refersToSameEntityAs |
P129687
|
FINISHED |
| Object | Unua |
—
|
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: Unua | Statement: [Onua, refersToSameEntityAs, Unua]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToSameEntityAs Context triple: [Onua, refersToSameEntityAs, Unua]
-
A.
identifiedAsSameObjectAs
chosen
Indicates that two referenced entities are recognized or treated as being the very same underlying object or instance.
-
B.
alsoRefersTo
Indicates that one term, label, or identifier is used as an alternative designation for the same entity or concept as another.
-
C.
samePersonAs
Indicates that two referenced entities are in fact the very same individual, not just similar or related.
-
D.
equivalentTo
Indicates that two entities represent the same concept, value, or state, and can be treated as interchangeable in the given context.
-
E.
refersToPerson
Indicates that one entity is making reference to, mentioning, or pointing specifically to a particular person.
- 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_69e2954222288190a7323554d0cca8d7 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d0d85d348190946b578e1a1c3bcc |
completed | April 29, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:22 p.m.