Triple
T37079414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oblation |
E917800
|
entity |
| Predicate | hasReplicaIn |
P205712
|
FINISHED |
| Object | UP Baguio campus |
E267493
|
NE 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: UP Baguio campus | Statement: [Oblation, hasReplicaIn, UP Baguio campus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReplicaIn Context triple: [Oblation, hasReplicaIn, UP Baguio campus]
-
A.
hasReplicaStatus
Indicates that one entity serves as a copy or duplicate of another, often with a specific role or state in a replication relationship.
-
B.
hasReplicaPolicy
Indicates that an entity is associated with a specific policy governing how its replicas are created, managed, or maintained.
-
C.
hasReplicaDisplays
Indicates that an entity features or presents one or more replica items as displays.
-
D.
hasReplicators
Indicates that an entity possesses or is equipped with devices or mechanisms capable of reproducing or duplicating objects, structures, or materials.
-
E.
hasReplicaShip
Indicates that one entity possesses or is associated with a ship that is a replica or reproduction of another ship.
- F. None of above. chosen
Provenance (5 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_69f76e9771e08190a690834e3cd20654 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3f6a0926a4819092c77608e5241234 |
completed | June 27, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:14 p.m.