Triple
T25768335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippine Military Academy |
E648944
|
entity |
| Predicate | reorganizedAsPMA |
P1504
|
FINISHED |
| Object | 1936 |
—
|
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: 1936 | Statement: [Philippine Military Academy, reorganizedAsPMA, 1936]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reorganizedAsPMA Context triple: [Philippine Military Academy, reorganizedAsPMA, 1936]
-
A.
reorganizedAs
chosen
Indicates that an existing entity has been restructured or reconfigured into a new organizational form or arrangement.
-
B.
reorganizedIn
Indicates that an entity underwent a structural or organizational change within a specified context, time, or framework.
-
C.
reorganized
Indicates that an entity has changed the structure, order, or arrangement of another entity or set of entities from a previous configuration.
-
D.
reorganizedFor
Indicates that one entity has been rearranged, restructured, or otherwise modified in its organization for the benefit, use, or requirements of another entity.
-
E.
reorganizedDueTo
Indicates that one entity was reorganized as a consequence of, or in response to, another specified factor, event, or condition.
- 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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fdf52c2c8190b2354e611031e929 |
completed | May 2, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 22, 2026, 5:12 a.m.