Triple
T37629821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birkirkara parish |
E936308
|
entity |
| Predicate | hasYouthGroup |
P153616
|
FINISHED |
| Object | Birkirkara parish youth group |
—
|
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: Birkirkara parish youth group | Statement: [Birkirkara parish, hasYouthGroup, Birkirkara parish youth group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasYouthGroup Context triple: [Birkirkara parish, hasYouthGroup, Birkirkara parish youth group]
-
A.
hasYouthTeam
Indicates that an entity has an associated youth team that serves as its junior or developmental squad.
-
B.
hasYouthProgram
Indicates that an entity offers or is associated with an organized program or set of activities specifically designed for young people.
-
C.
hasYouthBase
Indicates that an entity has an associated youth-level base, such as a junior or developmental organization, facility, or team structure.
-
D.
hasYouthMinistryOffice
chosen
Indicates that an entity has an office or designated space specifically for its youth ministry activities.
-
E.
hasYoungAdultMember
Indicates that an entity includes at least one member who is classified as a young adult.
- 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_69f76ed24820819081bafd36e9088701 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa1321b48190af92a3e7ec24ec5b |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.