Triple
T37079414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oblation |
E917800
|
entity |
| Predicate | hasReplicaIn |
—
|
GENERATED |
| Object | UP Baguio campus |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
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 (1 batch)
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. |
Created at: May 3, 2026, 4:14 p.m.