Triple
T32510080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Croft family |
E830906
|
entity |
| Predicate | developerAssociated |
P139242
|
FINISHED |
| Object | Core Design |
—
|
NE NERFINISHED |
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: Core Design | Statement: [Croft family, developerAssociated, Core Design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developerAssociated Context triple: [Croft family, developerAssociated, Core Design]
-
A.
developerOfWork
Indicates that one entity is the creator or producer responsible for making or developing a particular work.
-
B.
coDeveloperOf
Indicates that two or more entities jointly developed or collaborated in creating the same project, product, or work.
-
C.
developmentLinkedTo
Indicates that the development or progression of one entity is causally or contextually connected to the development or progression of another entity.
-
D.
hasDeveloperRelation
chosen
Indicates a relationship in which one entity serves as the developer, creator, or builder of another entity.
-
E.
developerRenamedTo
Indicates that a developer previously known by one name is now identified by a new name.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 1, 2026, 1 a.m.