Triple
T1496183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church |
E29690
|
entity |
| Predicate | hasFrequencyCategory |
P28499
|
FINISHED |
| Object | common English surname |
—
|
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: common English surname | Statement: [Church, hasFrequencyCategory, common English surname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFrequencyCategory Context triple: [Church, hasFrequencyCategory, common English surname]
-
A.
hasFrequencyNote
Indicates that something is associated with a specific note describing how often it occurs or is repeated.
-
B.
usesFrequency
Indicates that one entity employs or operates another entity at a specified rate, interval, or number of occurrences over time.
-
C.
hasCarrierFrequency
Indicates that an entity (such as a signal or transmission) is associated with a specific carrier frequency at which it is transmitted or modulated.
-
D.
hasNumberCategory
Indicates that an entity is associated with a specific numerical classification or type.
-
E.
isFrequently
Indicates that an action, state, or relationship occurs often or with high regularity between the related entities.
- 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_69a498dba1d8819093b46a3a8d2485f1 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6ec70c48190a94f6e1002848eae |
completed | March 1, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69a4c48a8cf48190a6ebf8d44a608a06 |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c4feea448190b2b5071b28a5b608 |
completed | March 1, 2026, 11 p.m. |
Created at: March 1, 2026, 8:12 p.m.