Triple
T19387013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sharon plain |
E484960
|
entity |
| Predicate | developedIntensivelyIn |
P45874
|
FINISHED |
| Object | 20th 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: 20th century | Statement: [Sharon plain, developedIntensivelyIn, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedIntensivelyIn Context triple: [Sharon plain, developedIntensivelyIn, 20th century]
-
A.
developedThrough
Indicates that something came into existence, was created, or was brought to its current form by means of a specified process, method, or developmental pathway.
-
B.
developedAlong
Indicates that something was created, constructed, or evolved following the course, path, or boundary of something else.
-
C.
developedWithin
chosen
Indicates that something was created, produced, or brought into existence inside a specified context, boundary, or time frame.
-
D.
developed
Indicates that one entity created, designed, or brought another entity into a more advanced or complete state through effort or work.
-
E.
hasDevelopmentFocus
Indicates that an entity is primarily concerned with or directed toward a particular area, goal, or aspect of development.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61b418f148190972b7b46038bc744 |
completed | April 20, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:36 p.m.