Triple
T21558771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabine salt trail |
E531959
|
entity |
| Predicate | resourceOrigin |
P87048
|
FINISHED |
| Object | coastal or salt-producing areas |
—
|
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: coastal or salt-producing areas | Statement: [Sabine salt trail, resourceOrigin, coastal or salt-producing areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resourceOrigin Context triple: [Sabine salt trail, resourceOrigin, coastal or salt-producing areas]
-
A.
registrationOrigin
Indicates the source or context from which a registration event was initiated or created.
-
B.
originSite
chosen
Indicates the place or site from which something or someone originally comes or is derived.
-
C.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
D.
physicalOrigin
Indicates that one entity is the place or source from which another entity physically originates or comes into existence.
-
E.
classOrigin
Indicates the original class or category from which an entity is derived, instantiated, or classified.
- 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eed2e21c5c8190aa32795e41f1550e |
completed | April 27, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:29 p.m.