Triple
T25585013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archduke Martin of Austria-Este |
E641355
|
entity |
| Predicate | hasHouseBranch |
P44973
|
FINISHED |
| Object | Austria-Este |
—
|
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: Austria-Este | Statement: [Archduke Martin of Austria-Este, hasHouseBranch, Austria-Este]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHouseBranch Context triple: [Archduke Martin of Austria-Este, hasHouseBranch, Austria-Este]
-
A.
houseBranch
chosen
Indicates that a particular house is a branch, subsidiary, or local unit of a larger parent organization or main house.
-
B.
hasCountryHouse
Indicates that one entity possesses or owns a house located in the countryside.
-
C.
hasBranchResidenceIn
Indicates that an organization maintains a branch or subsidiary located in a specified place or jurisdiction.
-
D.
hasBranchOffice
Indicates that one organization maintains a branch office or subsidiary location in another place or entity.
-
E.
hasTotalEarthlyBranches
Indicates that an entity is associated with a specific total number of Earthly Branches (e.g., in a cyclical or calendrical system).
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 21, 2026, 4:15 p.m.