Triple
T30970637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OFMCap |
E789086
|
entity |
| Predicate | denotesBranchOf |
P12137
|
FINISHED |
| Object | Franciscan Order |
—
|
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: Franciscan Order | Statement: [OFMCap, denotesBranchOf, Franciscan Order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denotesBranchOf Context triple: [OFMCap, denotesBranchOf, Franciscan Order]
-
A.
subbranchOf
Indicates that one entity is a subordinate or secondary branch derived from, and structurally dependent on, another entity.
-
B.
isUniqueBranchOf
Indicates that one branch is the sole or distinct sub-branch associated with a particular parent entity or structure.
-
C.
isPartOfBranchTypically
Indicates that something is typically a component or subdivision within a larger branch.
-
D.
isAnabranchOf
Indicates that one watercourse branches off from a main river or stream and later rejoins it, forming a secondary channel of the same system.
-
E.
branchesFrom
chosen
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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 8:54 p.m.