Triple
T5557523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Company for Gertrude |
E145682
|
entity |
| Predicate | hasMainSettingType |
P28105
|
FINISHED |
| Object | country house |
—
|
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: country house | Statement: [Company for Gertrude, hasMainSettingType, country house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainSettingType Context triple: [Company for Gertrude, hasMainSettingType, country house]
-
A.
hasSetting
Indicates that an entity takes place, occurs, or exists within a particular environment, context, or location.
-
B.
hasNotableSettingBy
Indicates that the subject has a notable or significant setting that was created, designed, or established by the specified entity.
-
C.
hasMainLocationType
chosen
Indicates that an entity is associated with a primary or predominant type of location that characterizes where it is mainly situated or operates.
-
D.
hasThemeType
Indicates that something is associated with or characterized by a particular thematic category or type.
-
E.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
- 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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01ffe12cc81908186f28ace0f4d82 |
completed | March 22, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.