Triple
T32490956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erik Andersen |
E830382
|
entity |
| Predicate | contributionNature |
P137171
|
FINISHED |
| Object | code development |
—
|
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: code development | Statement: [Erik Andersen, contributionNature, code development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contributionNature Context triple: [Erik Andersen, contributionNature, code development]
-
A.
sharesNatureWith
Indicates that two entities possess the same fundamental characteristics, qualities, or essence.
-
B.
scriptNature
Indicates that something concerns the inherent characteristics, type, or functional role of a script (e.g., its purpose, behavior, or classification).
-
C.
partnershipNature
Indicates the type or characteristics of the partnership relationship that exists between the involved entities.
-
D.
contributionBased
Indicates that something is determined, allocated, or structured according to the level or amount of contributions made by the involved entities.
-
E.
relatesToNatureOf
chosen
Indicates a general relationship that concerns or characterizes the inherent nature, essence, or fundamental qualities of something.
- 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_69f34920aa4081908d8fb0277414b911 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: May 1, 2026, 12:59 a.m.