Triple
T20595342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hufflepuff |
E506035
|
entity |
| Predicate | houseFounderEra |
P69762
|
FINISHED |
| Object | 10th century |
—
|
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: 10th century | Statement: [Hufflepuff, houseFounderEra, 10th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: houseFounderEra Context triple: [Hufflepuff, houseFounderEra, 10th century]
-
A.
ownerAtFounding
Indicates that an entity is the owner of another entity at the time the latter is founded or established.
-
B.
foundingAround
chosen
Indicates that an entity was founded at approximately, but not exactly, the specified time or within a loosely defined surrounding period.
-
C.
houseFoundedFrom
Indicates that a house, organization, or lineage was established or originated from a specified source, predecessor, or founding entity.
-
D.
possiblyFoundedBy
Indicates that an entity may have been founded or established by another entity, but this founding relationship is uncertain or not definitively confirmed.
-
E.
foundedBefore
Indicates that one entity was established or created at an earlier time than the other 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_69e0b4ba6ae88190af871e1f9522c704 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aa1b1c6c8190a2d85e7a390fc6a5 |
completed | April 20, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:40 a.m.