Triple
T16178909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esperantists |
E392635
|
entity |
| Predicate | sharesIdentity |
P108480
|
FINISHED |
| Object | Esperanto speaker |
—
|
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: Esperanto speaker | Statement: [Esperantists, sharesIdentity, Esperanto speaker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesIdentity Context triple: [Esperantists, sharesIdentity, Esperanto speaker]
-
A.
sharesIdentityWith
Indicates that two entities are considered to have the same identity, referring to the very same underlying individual or object rather than merely being similar or related.
-
B.
relatedIdentity
chosen
Indicates that two identities are connected or associated with each other in some meaningful way, such as being alternate, linked, or otherwise contextually related.
-
C.
shareRegionalIdentityWith
Indicates that two entities are perceived to belong to or identify with the same geographic, cultural, or regional community.
-
D.
sharesMembersWith
Indicates that two groups or collections have one or more members in common.
-
E.
sharesElementsWith
Indicates that two entities have one or more elements or components in common.
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2205ab3108190a84fc2dfe61d5044 |
completed | April 17, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.