Triple
T4379020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dávid |
E99081
|
entity |
| Predicate | isUsedInCommunity |
P5924
|
FINISHED |
| Object | Hungarian diaspora |
—
|
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: Hungarian diaspora | Statement: [Dávid, isUsedInCommunity, Hungarian diaspora]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedInCommunity Context triple: [Dávid, isUsedInCommunity, Hungarian diaspora]
-
A.
usedInCommunity
chosen
Indicates that something is employed, practiced, or applied within a particular community or communal context.
-
B.
usedByCommunity
Indicates that something is utilized or adopted collectively by a particular community.
-
C.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
D.
developedInCommunity
Indicates that something was created, built, or advanced through the participation, collaboration, or support of a particular community.
-
E.
includesCommunity
Indicates that one entity encompasses, contains, or has within it a particular community as part of its scope or composition.
- 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_69b3454ea8f48190a49c2436624d6ef6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35240092c81908e26ff607d665e7a |
completed | March 12, 2026, 11:54 p.m. |
| PD | Predicate disambiguation | batch_69b34f557fe8819085032bf7f0cea5dc |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:18 p.m.