Triple
T27453486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fore Street |
E692514
|
entity |
| Predicate | usesSourcingPractice |
P38247
|
FINISHED |
| Object | local sourcing |
—
|
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: local sourcing | Statement: [Fore Street, usesSourcingPractice, local sourcing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSourcingPractice Context triple: [Fore Street, usesSourcingPractice, local sourcing]
-
A.
usesIngredientSourcing
Indicates that one entity obtains or incorporates another entity as a source of ingredients in its operations or products.
-
B.
usesSourceType
chosen
Indicates that one entity makes use of, relies on, or operates based on a particular type or category of source.
-
C.
usedAsSourceIn
Indicates that something serves as the origin, basis, or input from which another thing is derived, produced, or obtained.
-
D.
usesSamplingOf
Indicates that one entity employs or relies on a sample or subset derived from another entity for its operation, analysis, or processing.
-
E.
usedInPractice
Indicates that something is actually applied or implemented in real-world practice rather than just being theoretical or proposed.
- 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_69ef5207903881909427745cda05d27a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 27, 2026, 12:48 p.m.