Triple
T38631182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mack Isbjørn |
E937456
|
entity |
| Predicate | producerFoundedIn |
P199997
|
FINISHED |
| Object | 1877 |
—
|
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: 1877 | Statement: [Mack Isbjørn, producerFoundedIn, 1877]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producerFoundedIn Context triple: [Mack Isbjørn, producerFoundedIn, 1877]
-
A.
madeByCompanyFoundedIn
Indicates that something was produced or created by a company whose founding took place in a specified time or place.
-
B.
coFoundedIn
Indicates that two or more entities jointly founded something (such as an organization or company) in a specific place or at a specific time.
-
C.
businessFoundedIn
Indicates that a business entity was established or came into existence in a specific location or time.
-
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.
producerName
Indicates that the associated value is the name of the producer responsible for creating or manufacturing the referenced entity.
- F. None of above. chosen
Provenance (4 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff691f5ae481908597ce245188d31c |
completed | May 9, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69ff67ceeeb081909fd00cad166c4b6a |
completed | May 9, 2026, 4:58 p.m. |
| PDg | Predicate description generation | batch_69ff691e86d0819099fdb5eca5a95632 |
completed | May 9, 2026, 5:04 p.m. |
Created at: May 3, 2026, 4:32 p.m.