Triple
T28452847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Brugeoise wooden cars |
E716624
|
entity |
| Predicate | serviceEntryYearApprox |
P160298
|
FINISHED |
| Object | 1913 |
—
|
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: 1913 | Statement: [La Brugeoise wooden cars, serviceEntryYearApprox, 1913]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceEntryYearApprox Context triple: [La Brugeoise wooden cars, serviceEntryYearApprox, 1913]
-
A.
enteredServiceApproximateYear
chosen
Indicates that an entity began its service or operation around a specified year, where the year is an approximate rather than an exact value.
-
B.
yearDeliveredApprox
Indicates that the year an item or entity was delivered is known only approximately, rather than as an exact calendar year.
-
C.
purchaseYear
Indicates the calendar year in which a purchase or acquisition of something took place.
-
D.
approximateYearOfImport
Indicates the estimated calendar year during which an import event occurred or an entity was brought into a system or location.
-
E.
yearOfManufacture
Indicates the specific calendar year in which an item was produced or manufactured.
- 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_69efd6b76f8c8190a7ba908aca280942 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 28, 2026, 1:52 a.m.