Triple
T9812757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Francis Johnson |
E238315
|
entity |
| Predicate | activityPeriodStart |
P4785
|
FINISHED |
| Object | late 16th 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: late 16th century | Statement: [Francis Johnson, activityPeriodStart, late 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activityPeriodStart Context triple: [Francis Johnson, activityPeriodStart, late 16th century]
-
A.
activityTime
Indicates the time period during which an activity occurs or is scheduled to take place.
-
B.
activityStartApprox
chosen
Indicates that the start time of an activity is known only approximately, rather than as an exact timestamp.
-
C.
typicalStartPeriod
Indicates the usual or standard time period during which something begins or is initiated.
-
D.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
-
E.
officeStartAfter
Indicates that one entity’s term or period in office begins after another specified time or event.
- 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_69ca84defac48190abc1148804f184c1 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb222ba788190a9085272a3de7852 |
completed | April 2, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69cd03e01ea881909a7d93fc3994ace5 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:30 p.m.