Triple
T187987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMTK |
E4024
|
entity |
| Predicate | markType |
P5686
|
FINISHED |
| Object | freight car mark |
—
|
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: freight car mark | Statement: [AMTK, markType, freight car mark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: markType Context triple: [AMTK, markType, freight car mark]
-
A.
notationType
Indicates the specific system or style of notation used to represent or encode something (such as music, math, or language).
-
B.
mentions
Indicates that one entity refers to, cites, or brings up another entity in some form of communication or content.
-
C.
demarcationType
Indicates the specific way in which a boundary or separation between entities is defined, marked, or categorized.
-
D.
badge
Indicates that one entity confers, displays, or is associated with a symbolic mark or emblem representing status, achievement, role, or affiliation in relation to another entity.
-
E.
characterizedBy
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
- F. None of above. chosen
Provenance (4 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a2594940e48190a3d8efbce46241c3 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a25672332081909386f35f3ca15dd2 |
completed | Feb. 28, 2026, 2:44 a.m. |
| PDg | Predicate description generation | batch_69a25738b5108190866fd704fceee18a |
completed | Feb. 28, 2026, 2:47 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.