Triple
T11822344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacquard loom |
E281169
|
entity |
| Predicate | programRepresentation |
P67580
|
FINISHED |
| Object | sequence of punched cards |
—
|
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: sequence of punched cards | Statement: [Jacquard loom, programRepresentation, sequence of punched cards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programRepresentation Context triple: [Jacquard loom, programRepresentation, sequence of punched cards]
-
A.
scriptRepresentation
Indicates the specific written or encoded form in which something (such as language, data, or content) is expressed or represented.
-
B.
programStructure
Indicates how components, modules, or elements are organized and related within a program or system.
-
C.
representsCode
chosen
Indicates that one entity serves as a code, encoding, or symbolic representation for another entity.
-
D.
componentRepresents
Indicates that one component stands in for, symbolizes, or models another entity or concept within a system or context.
-
E.
representationIn
Indicates that one entity serves as a depiction, model, or stand-in for another entity within a given context or medium.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5e9c50481909b2287a0b23d2094 |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.