Triple
T11279058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Stanly |
E267011
|
entity |
| Predicate | time period of activity |
P302
|
FINISHED |
| Object | early 19th century |
—
|
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: early 19th century | Statement: [John Stanly, time period of activity, early 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: time period of activity Context triple: [John Stanly, time period of activity, early 19th century]
-
A.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
B.
activityTime
Indicates the time period during which an activity occurs or is scheduled to take place.
-
C.
timePeriodCategory
Indicates the classification of a time period into a specific category or type (e.g., era, phase, or temporal grouping).
-
D.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
-
E.
timePeriodEvent
Indicates that an event occurs, is scheduled, or is valid within a specified time 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e969b3448190940e2bd499d2d7de |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a240588190aa097298f951c915 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:31 p.m.