Triple
T6890971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All Saints |
E159043
|
entity |
| Predicate | hasCollectiveTitleFor |
P57464
|
FINISHED |
| Object | all known saints |
—
|
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: all known saints | Statement: [All Saints, hasCollectiveTitleFor, all known saints]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollectiveTitleFor Context triple: [All Saints, hasCollectiveTitleFor, all known saints]
-
A.
titleHoldersCollectively
chosen
Indicates that a group of entities jointly hold, share, or possess a particular title or set of titles as a collective.
-
B.
hasCollectiveCharacter
Indicates that a group or set of entities is treated as a unified whole, sharing a collective nature or identity rather than being considered solely as separate individuals.
-
C.
hasLatinTitleOf
Indicates that one entity has, uses, or is associated with the Latin-language title corresponding to another entity.
-
D.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
E.
hasTitleFrom
Indicates that one entity holds or uses a title that originates from, or is conferred by, another entity.
- 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_69c6883568c8819081db6407e892cccc |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d92d45f08190a730b3842c95b521 |
completed | March 27, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b53e9881909ec298daa9f1913b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:24 p.m.