Triple
T36770184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kartilya ng Katipunan |
E908452
|
entity |
| Predicate | organizationDocumentOf |
P84456
|
FINISHED |
| Object | Katipunan |
—
|
NE NERFINISHED |
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: Katipunan | Statement: [Kartilya ng Katipunan, organizationDocumentOf, Katipunan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizationDocumentOf Context triple: [Kartilya ng Katipunan, organizationDocumentOf, Katipunan]
-
A.
organOrganization
Indicates that an organ is structurally or functionally part of, or associated with, a specific organization or organizational system.
-
B.
organizationDesired
Indicates that one entity is the organization that another entity wants, prefers, or aims to be associated with.
-
C.
directoryOrganization
Indicates that one entity is organized or structured as a directory for another entity, typically grouping or arranging related items or records.
-
D.
organizationDescribedBy
chosen
Indicates that an organization is characterized, detailed, or explained by a particular description or document.
-
E.
formsOrganization
Indicates that an entity initiates or creates a new organization or formal group.
- 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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: May 3, 2026, 4:12 p.m.