Triple
T2169050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of the Philippines Manila |
E46979
|
entity |
| Predicate | mergedIntoUP |
P77
|
FINISHED |
| Object | 1910 |
—
|
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: 1910 | Statement: [University of the Philippines Manila, mergedIntoUP, 1910]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergedIntoUP Context triple: [University of the Philippines Manila, mergedIntoUP, 1910]
-
A.
mergedInto
chosen
Indicates that one entity has been combined with and absorbed into another entity, ceasing to exist as a separate unit.
-
B.
mergedBy
Indicates that one entity is combined or integrated into another entity through the action or decision of a specific agent.
-
C.
mergedInstitution
Indicates that one institution has combined with another to form a single, unified institution.
-
D.
reintegratedInto
Indicates that an entity has been brought back and incorporated again into a group, system, or context it was previously separated from.
-
E.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
- 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_69a88a184cbc8190877791f6552c2484 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc1559ff481908efe3f214b2570dc |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbd9efc1c81909a65044a1ffc9038 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.