Triple
T1416314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Cranch |
E31924
|
entity |
| Predicate | hasActivityPeriod |
P10350
|
FINISHED |
| Object | late 18th 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 18th century | Statement: [William Cranch, hasActivityPeriod, late 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasActivityPeriod Context triple: [William Cranch, hasActivityPeriod, late 18th century]
-
A.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
B.
hasActivityStatus
Indicates the current state or condition of an activity, such as whether it is planned, ongoing, completed, or cancelled.
-
C.
hasActivityType
Indicates the specific kind or category of activity associated with an entity or event.
-
D.
activityTime
chosen
Indicates the time period during which an activity occurs or is scheduled to take place.
-
E.
hasKeyActivity
Indicates that an entity is associated with or performs a primary or central activity.
- 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c403ccdc8190b2a5fda037b6ea34 |
completed | March 1, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69a4bf060b0081909ba00e6ac093a28b |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.