Triple
T6615504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brouwer Route |
E149339
|
entity |
| Predicate | usedIntoCentury |
P16875
|
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: [Brouwer Route, usedIntoCentury, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedIntoCentury Context triple: [Brouwer Route, usedIntoCentury, 18th century]
-
A.
usedInCentury
chosen
Indicates that something (such as an object, practice, or concept) was in use during a specified century.
-
B.
usedSinceCentury
Indicates that something has been in use starting from a specified century.
-
C.
endedInCentury
Indicates that an event, period, or process concluded during a specified century.
-
D.
usedAsMintInCentury
Indicates that an entity functioned as a mint (coin-producing facility) during a specified century.
-
E.
formedInCentury
Indicates that an entity (such as an organization, group, or structure) was established or came into existence during a specified century.
- 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_69c687ebc680819094caf71faba2efe2 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6bdb88cc881908f35648c15a7dc85 |
completed | March 27, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69c6ad007c1c8190af425f51011c7ad1 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:57 p.m.