Triple
T8292856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stannary courts |
E193941
|
entity |
| Predicate | appliedToActivity |
P35065
|
FINISHED |
| Object | tin mining |
—
|
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: tin mining | Statement: [Stannary courts, appliedToActivity, tin mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToActivity Context triple: [Stannary courts, appliedToActivity, tin mining]
-
A.
appliedBy
Indicates that an action, process, or treatment is carried out or executed by a particular agent or entity.
-
B.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
C.
appliedAs
Indicates that one entity submitted itself or was put forward for consideration in a particular role, position, or context relative to another entity.
-
D.
appliesAt
Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
-
E.
targetedActivity
chosen
Indicates that an activity is specifically directed or focused toward a particular entity, group, or objective.
- 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7c9deb50819086ae9c97b03fefc3 |
completed | March 31, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:52 p.m.