Triple
T28047455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jarrell Plantation State Historic Site |
E708721
|
entity |
| Predicate | alsoProduced |
P104304
|
FINISHED |
| Object | syrup |
—
|
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: syrup | Statement: [Jarrell Plantation State Historic Site, alsoProduced, syrup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoProduced Context triple: [Jarrell Plantation State Historic Site, alsoProduced, syrup]
-
A.
alsoProducedAs
Indicates that the same work, content, or product has been created or released in an additional form, version, or medium.
-
B.
coProduced
Indicates that two or more entities jointly produced or created a work, project, or product together.
-
C.
alsoProducedInPattern
chosen
Indicates that something was additionally produced within the same pattern, process, or production context as another item or event.
-
D.
associatedProduction
Indicates that there is a related or connected production (such as a work, performance, or manufacturing process) linked to the subject entity.
-
E.
coProductionType
Indicates the specific nature or category of a collaborative production relationship between multiple producing entities.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f63fd79e4c8190af9263b679e5ff07 |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 8:30 p.m.