Triple
T19775345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ad hoc committees of the United States Conference of Catholic Bishops |
E474988
|
entity |
| Predicate | useOfTerm |
P137294
|
FINISHED |
| Object | ad hoc committee |
—
|
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: ad hoc committee | Statement: [ad hoc committees of the United States Conference of Catholic Bishops, useOfTerm, ad hoc committee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useOfTerm Context triple: [ad hoc committees of the United States Conference of Catholic Bishops, useOfTerm, ad hoc committee]
-
A.
usedTerm
Indicates that one entity employed, referenced, or applied a particular term in some context.
-
B.
usesTerminologyFrom
Indicates that one entity adopts or incorporates the specialized terms or vocabulary originating from another entity or source.
-
C.
definesUseOf
Indicates that one entity specifies or determines how another entity is to be used or applied.
-
D.
hasConceptualUse
Indicates that one entity is used or applied in a conceptual, abstract, or theoretical way by another entity.
-
E.
usesTermForCommunity
Indicates that one entity refers to or designates a community using a particular term.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6535fb114819089911ed3ba6565c0 |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:48 p.m.