Triple
T23481886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Crate |
E570426
|
entity |
| Predicate | crateMarking |
P35665
|
FINISHED |
| Object | Arctic Expedition – June 19, 1834 |
—
|
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: Arctic Expedition – June 19, 1834 | Statement: [The Crate, crateMarking, Arctic Expedition – June 19, 1834]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crateMarking Context triple: [The Crate, crateMarking, Arctic Expedition – June 19, 1834]
-
A.
seedMarking
Indicates that an entity bears or applies a specific mark, pattern, or label associated with seeds.
-
B.
armorMarkings
Indicates that one entity bears specific markings, patterns, or insignia on its armor in relation to another entity or context.
-
C.
coatMarkings
Indicates how an entity’s coat is patterned or marked, such as stripes, spots, or other distinctive visual markings.
-
D.
distinctiveMarking
Indicates that one entity bears a unique or distinguishing visual feature or pattern that sets it apart from others.
-
E.
marksOn
chosen
Indicates that one entity bears visible signs, traces, or imprints that have been made or left by another entity.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a75118048190b4af687906c4e747 |
completed | April 29, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:03 p.m.