Triple
T135636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esperanto |
E2739
|
entity |
| Predicate | hasCommunityNameForSpeakers |
P1519
|
FINISHED |
| Object | Esperantists |
—
|
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: Esperantists | Statement: [Esperanto, hasCommunityNameForSpeakers, Esperantists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunityNameForSpeakers Context triple: [Esperanto, hasCommunityNameForSpeakers, Esperantists]
-
A.
usedCollectiveName
chosen
Indicates that a group of entities is referred to by a shared collective name.
-
B.
hasCommunitySpace
Indicates that an entity provides or includes a shared physical or virtual area intended for communal use, activities, or gatherings.
-
C.
hasCommunityType
Indicates that an entity is associated with or classified under a particular type or category of community.
-
D.
hasAudience
Indicates that an entity is intended to be received, viewed, or engaged with by a particular group of people.
-
E.
hasApproximateTotalSpeakers
Indicates that an entity is associated with an estimated or roughly calculated number of total speakers, rather than an exact count.
- 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257a3ad908190b6a8652f09ae0cbb |
completed | Feb. 28, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69a25651b9048190a6277b7fec98c1ea |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.