Triple
T816119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jython |
E17654
|
entity |
| Predicate | developerCommunity |
P6194
|
FINISHED |
| Object | Jython developers |
—
|
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: Jython developers | Statement: [Jython, developerCommunity, Jython developers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developerCommunity Context triple: [Jython, developerCommunity, Jython developers]
-
A.
developmentRole
Indicates that an entity participates in the creation, design, or production of another entity in a specific developmental capacity or function.
-
B.
community
chosen
Indicates a relationship where individuals or groups are connected by shared location, interests, or identity, forming a collective social unit.
-
C.
usedInCommunity
Indicates that something is employed, practiced, or applied within a particular community or communal context.
-
D.
usedByCommunity
Indicates that something is utilized or adopted collectively by a particular community.
-
E.
supportsCommunity
Indicates that one entity provides assistance, resources, or encouragement that benefits a community or group.
- 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_69a4937bcaac8190a322524ac6f45a5a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ab5157b08190b6c8f2fd455f261e |
completed | March 1, 2026, 9:10 p.m. |
| PD | Predicate disambiguation | batch_69a4aa756920819080ae82948974c876 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.