Triple
T27134716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count of Wisborg |
E681650
|
entity |
| Predicate | holderOrigin |
P162624
|
FINISHED |
| Object | members of the Swedish royal house living abroad |
—
|
LITERAL 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: members of the Swedish royal house living abroad | Statement: [Count of Wisborg, holderOrigin, members of the Swedish royal house living abroad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holderOrigin Context triple: [Count of Wisborg, holderOrigin, members of the Swedish royal house living abroad]
-
A.
holderOrigin
chosen
Indicates that one entity is the original source, creator, or origin point from which the holder entity derives, is issued, or established.
-
B.
holderIs
Indicates that one entity serves as the holder, possessor, or container of another entity.
-
C.
registrationOrigin
Indicates the source or context from which a registration event was initiated or created.
-
D.
holder
Indicates that one entity possesses, controls, or has custody of another entity, typically in a temporary or contextual sense.
-
E.
holderMayBe
Indicates that a particular entity is allowed or permitted to serve as the holder or possessor of another entity.
- 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 9:06 a.m.