Triple
T12013690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fielder Jones |
E285969
|
entity |
| Predicate | managedDuringPeriod |
P39991
|
FINISHED |
| Object | 1900s |
—
|
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: 1900s | Statement: [Fielder Jones, managedDuringPeriod, 1900s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managedDuringPeriod Context triple: [Fielder Jones, managedDuringPeriod, 1900s]
-
A.
modifiedDuring
Indicates that one entity underwent a change or alteration while another specified time period, process, or event was occurring.
-
B.
managedUntil
chosen
Indicates that one entity was responsible for managing or overseeing another entity up to a specific point in time.
-
C.
ownedDuring
Indicates that one entity possessed or held ownership of another entity for some or all of a specified time interval.
-
D.
maintainedDuring
Indicates that a certain condition, state, or relationship continues to hold throughout the duration of a specified event or time interval.
-
E.
scheduledDuring
Indicates that one event or activity is planned to occur within the time interval defined by another event or period.
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903d884488190b4450a98088208ef |
completed | April 10, 2026, 2:06 p.m. |
| PD | Predicate disambiguation | batch_69d902b245cc8190af96a9c2bd9c6250 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.