Triple
T2021744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surveyor of the Port of Salem |
E44118
|
entity |
| Predicate | timeOfExistence |
P12795
|
FINISHED |
| Object | 19th century United States customs system |
—
|
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: 19th century United States customs system | Statement: [Surveyor of the Port of Salem, timeOfExistence, 19th century United States customs system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfExistence Context triple: [Surveyor of the Port of Salem, timeOfExistence, 19th century United States customs system]
-
A.
timeExistence
chosen
Indicates the period or duration during which an entity exists or is valid.
-
B.
existsSince
Indicates that an entity has been in existence or valid from a specified point in time onward.
-
C.
existedUntil
Indicates that an entity continued to exist up to, but not necessarily beyond, a specified time or event.
-
D.
locationPeriod
Indicates that an entity is associated with being at a particular location during a specified time period.
-
E.
durationOfUse
Indicates the length of time for which something is used or remains in use.
- 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8efbe148190901d3650aa60408a |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a389408190a84a54856352f15b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.