Triple
T18255774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perl Mongers |
E437219
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | Perl Mongers |
—
|
NE NERFINISHED |
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: Perl Mongers | Statement: [Perl Mongers, name, Perl Mongers]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Perl Mongers Context triple: [Perl Mongers, name, Perl Mongers]
-
A.
Perl Mongers
chosen
Perl Mongers is a worldwide network of user groups dedicated to supporting and promoting the Perl programming language and its community.
-
B.
Perl community
The Perl community is a global, collaborative network of programmers, users, and contributors who develop, maintain, and support the Perl programming language and its ecosystem.
-
C.
The Perl Foundation
The Perl Foundation is a non-profit organization that supports the development, promotion, and community infrastructure of the Perl programming language.
-
D.
Perl 5 porters
Perl 5 porters is the core development team responsible for maintaining and advancing the Perl 5 programming language.
-
E.
Perl conferences
Perl conferences are gatherings of developers and enthusiasts focused on the Perl programming language, featuring technical talks, workshops, and community networking.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4fd85ee548190a102611fcf709ad4 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 10:34 a.m.