Triple
T9177213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buff Orpington |
E220230
|
entity |
| Predicate | wasDevelopedIn |
P86667
|
FINISHED |
| Object | late 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: late 19th century | Statement: [Buff Orpington, wasDevelopedIn, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasDevelopedIn Context triple: [Buff Orpington, wasDevelopedIn, late 19th century]
-
A.
alsoDevelopedIn
Indicates that something was additionally developed in another context, location, or environment beyond the primary one already specified.
-
B.
developedAs
Indicates that one entity was created, designed, or evolved specifically to function as or replace another entity.
-
C.
developedUnder
Indicates that something was created, produced, or brought into existence while being subject to the authority, guidance, or conditions imposed by a particular person, organization, regime, or framework.
-
D.
firstDeveloped
Indicates that one entity was the earliest to create, originate, or bring another entity into existence.
-
E.
developedWith
Indicates that something was created, built, or produced using a specified tool, technology, method, or collaborator.
- F. None of above. chosen
Provenance (4 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_69ca83e589948190ac9907819db11ddf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccbfa60c3c8190b6335b9067de5b72 |
completed | April 1, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69cc660761d88190ab6134b43b376964 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc66d7bf648190b8bff5b584b84975 |
completed | April 1, 2026, 12:29 a.m. |
Created at: March 30, 2026, 7:23 p.m.