Triple
T26243935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cedar system |
E656390
|
entity |
| Predicate | mainApplicationDomain |
P163098
|
FINISHED |
| Object | software 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: software development | Statement: [Cedar system, mainApplicationDomain, software development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainApplicationDomain Context triple: [Cedar system, mainApplicationDomain, software development]
-
A.
originalApplicationDomain
Indicates the domain or field in which something was first designed, intended, or primarily applied.
-
B.
hasApplicationDomain
Indicates that something is associated with, used in, or relevant to a particular field, area, or domain of application.
-
C.
defaultDomain
Indicates that one entity serves as the standard or primary domain associated with another entity, used when no more specific domain is specified.
-
D.
keyApplicationDomain
chosen
Indicates the primary field or area of use in which something (e.g., a method, tool, or concept) is mainly applied or intended to operate.
-
E.
mainStartingPoint
Indicates the primary location or position from which an event, process, or path begins.
- 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_69ee5b4c59a881909d9ee4fd013fffd5 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 26, 2026, 9:04 p.m.