Triple
T27502842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippine Marine Corps |
E694205
|
entity |
| Predicate | parentServiceBranch |
P29484
|
FINISHED |
| Object | Philippine Navy |
—
|
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: Philippine Navy | Statement: [Philippine Marine Corps, parentServiceBranch, Philippine Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentServiceBranch Context triple: [Philippine Marine Corps, parentServiceBranch, Philippine Navy]
-
A.
parentBranch
Indicates that one branch serves as the direct ancestor or source from which another branch originates or is derived.
-
B.
parentService
chosen
Indicates that one service functions as the higher-level or owning service in relation to another, which depends on or is derived from it.
-
C.
parentFrom
Indicates that one entity is the parent (biological, adoptive, or legal) of another entity.
-
D.
siblingBranch
Indicates that two branches share the same immediate parent node in a hierarchical structure, making them parallel or peer branches.
-
E.
branchesFrom
Indicates that one entity originates or diverges from another as a subordinate or offshoot path, structure, or lineage.
- 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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 27, 2026, 1:12 p.m.