Triple
T16178906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esperantists |
E392635
|
entity |
| Predicate | sharesPractice |
P116886
|
FINISHED |
| Object | using Esperanto in international meetings |
—
|
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: using Esperanto in international meetings | Statement: [Esperantists, sharesPractice, using Esperanto in international meetings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesPractice Context triple: [Esperantists, sharesPractice, using Esperanto in international meetings]
-
A.
sharesPracticesWith
chosen
Indicates that two entities engage in or follow similar methods, behaviors, or operational practices.
-
B.
sharesPrinciple
Indicates that two or more entities are based on, guided by, or adhere to the same underlying principle or fundamental rule.
-
C.
share
Indicates that one entity gives, divides, or jointly uses a resource, item, or information with another entity.
-
D.
sharesWorkWith
Indicates that one entity collaborates or participates jointly in work or tasks with another entity.
-
E.
sharesTrainingWith
Indicates that two entities have participated in the same training activity, program, or session.
- 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.