Triple
T35335286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of Groningen |
E1020433
|
entity |
| Predicate | earlyFunction |
P183035
|
FINISHED |
| Object | fortified trading center |
—
|
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: fortified trading center | Statement: [History of Groningen, earlyFunction, fortified trading center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlyFunction Context triple: [History of Groningen, earlyFunction, fortified trading center]
-
A.
earlyUse
Indicates that an entity is used or adopted at an unusually early time or stage relative to a typical or expected point of use.
-
B.
earlyPhase
Indicates that the related process, project, or development is in its initial or beginning stage.
-
C.
earlyContext
Indicates that something occurs, is provided, or is considered at an initial or preliminary stage relative to a process, event, or reference point.
-
D.
earlyActivity
Indicates that an entity begins or performs a specified activity earlier than a usual, expected, or referenced time.
-
E.
earlyStrategy
Indicates that an entity adopts or implements a strategy at an early stage or time relative to a process, event, or development.
- 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_69f76debb4e08190be52d89b8af2392d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f795b5228c8190adb5bf86e581f70c |
completed | May 3, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f79527c7bc8190a69d87bec01f65c8 |
completed | May 3, 2026, 6:34 p.m. |
Created at: May 3, 2026, 4:03 p.m.