Triple
T18133188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porto Cervo |
E434066
|
entity |
| Predicate | developmentStartedIn |
P11886
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [Porto Cervo, developmentStartedIn, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developmentStartedIn Context triple: [Porto Cervo, developmentStartedIn, 1960s]
-
A.
developmentBegan
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
-
B.
developmentStart
chosen
Indicates the point in time or event when the development process of something begins.
-
C.
developedWithin
Indicates that something was created, produced, or brought into existence inside a specified context, boundary, or time frame.
-
D.
developmentOpened
Indicates that a development project, phase, or environment has been initiated and made active or accessible.
-
E.
developmentEnded
Indicates that the process of creating, improving, or expanding something has been completed and no further development is taking place.
- 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de04321c81909c0b9d47757720fd |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.