Triple
T5973599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amsterdam civic guild system |
E132931
|
entity |
| Predicate | declinesDuring |
P2924
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Amsterdam civic guild system, declinesDuring, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declinesDuring Context triple: [Amsterdam civic guild system, declinesDuring, 18th century]
-
A.
declineAfter
Indicates that one entity or value decreases or worsens following another specified event, condition, or point in time.
-
B.
declineIn
Indicates a relationship where one entity experiences a decrease or reduction in the level, amount, or intensity of another entity over time.
-
C.
declineBeganInPeriod
Indicates that the onset of a decline in the subject occurred during the specified time period.
-
D.
declinedDuring
chosen
Indicates that one entity’s value, condition, or status decreased over the course of a specified time period or event.
-
E.
decline
Indicates a decrease or reduction in the level, amount, quality, or intensity of something over time.
- 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_69c0086deab081908550159ca23eec9b |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04dc2243c8190bd3488e7b24af985 |
completed | March 22, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c049dcb3c081908ccc9b4d4b210229 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:03 p.m.