Triple
T26936637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christifideles Laici |
E678402
|
entity |
| Predicate | hasAddresseeGroup |
P61620
|
FINISHED |
| Object | lay faithful |
—
|
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: lay faithful | Statement: [Christifideles Laici, hasAddresseeGroup, lay faithful]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAddresseeGroup Context triple: [Christifideles Laici, hasAddresseeGroup, lay faithful]
-
A.
mainAddresseeGroup
chosen
Indicates that a specified group is the primary intended recipient or audience of a message, communication, or address.
-
B.
hasNotableRecipientGroup
Indicates that an entity is associated with a specific group that is recognized as a notable or distinguished recipient of something (e.g., an award, benefit, or honor).
-
C.
hasAttendeeGroup
Indicates that an event or activity is associated with a specific group of attendees considered collectively.
-
D.
hasRepresentativeGroup
Indicates that an entity is associated with, or formally represented by, a specific group acting on its behalf.
-
E.
hasGroupMember
Indicates that a group or collection includes a specific entity as one of its members.
- 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_69eeeb4cac908190a45956c2993d1cc2 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 27, 2026, 6:16 a.m.