Triple
T320595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippine Independent Church |
E6405
|
entity |
| Predicate | mainClassification |
P87
|
FINISHED |
| Object | Old Catholic-related |
—
|
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: Old Catholic-related | Statement: [Philippine Independent Church, mainClassification, Old Catholic-related]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainClassification Context triple: [Philippine Independent Church, mainClassification, Old Catholic-related]
-
A.
classificationStart
Indicates the point in time or process at which a classification or categorization of an entity begins.
-
B.
classificationSystem
Indicates a relationship where an entity is organized or categorized according to a particular classification scheme or taxonomy.
-
C.
researchClassification
Indicates that an entity is assigned a specific category or type within a research-related classification scheme.
-
D.
category
chosen
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
-
E.
previousClassification
Indicates that one classification precedes another in time or in an ordered sequence of classifications.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea8047c08190872c875e00f6e7dd |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e946607081909c8b97473aaf8d1b |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.