Triple
T18452398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Lovelace |
E450814
|
entity |
| Predicate | linkedToField |
P6979
|
FINISHED |
| Object | history of computing |
—
|
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: history of computing | Statement: [Earl of Lovelace, linkedToField, history of computing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToField Context triple: [Earl of Lovelace, linkedToField, history of computing]
-
A.
relatedField
chosen
Indicates that one field, topic, or area of study is connected or relevant to another in subject matter or application.
-
B.
linkedToStatement
Indicates that one entity is associated or connected to a particular statement, typically as a reference, support, or contextual link.
-
C.
linkedToDate
Indicates that an entity is associated or connected to a specific date or point in time.
-
D.
linkedByStructure
Indicates that two entities are connected or associated through a shared structural element, configuration, or framework.
-
E.
linkedToPort
Indicates that one entity is connected or associated with a specific port, such as a network, hardware, or interface port.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5264906cc8190b8b2cb77ec93d480 |
completed | April 19, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:31 a.m.