Triple
T2173529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catholic Legion of Decency |
E48475
|
entity |
| Predicate | CMeans |
P37398
|
FINISHED |
| Object | condemned |
—
|
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: condemned | Statement: [Catholic Legion of Decency, CMeans, condemned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CMeans Context triple: [Catholic Legion of Decency, CMeans, condemned]
-
A.
clusterDensity
Indicates the degree to which elements within a cluster are closely packed or concentrated relative to its size or volume.
-
B.
machineLearningLibrary
Indicates that one entity is a software library or framework specifically designed to support machine learning tasks for another entity.
-
C.
computationalClass
Indicates that two entities share the same computational complexity class or that one entity is categorized within a specified computational complexity class.
-
D.
kernelType
Indicates the specific kind or category of kernel associated with or used by an entity.
-
E.
centerOfDiversity
Indicates the location where a particular group, trait, or phenomenon exhibits its greatest variety or concentration of diversity.
- F. None of above. chosen
Provenance (4 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_69a88aa3faa48190995b233af6525815 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc1559ff481908efe3f214b2570dc |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbd9efc1c81909a65044a1ffc9038 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abc153b22481908115e5f582c93f12 |
completed | March 7, 2026, 6:10 a.m. |
Created at: March 4, 2026, 7:45 p.m.