Triple
T26265656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kasarvadavali |
E656974
|
entity |
| Predicate | developingStatus |
P67385
|
FINISHED |
| Object | rapidly developing |
—
|
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: rapidly developing | Statement: [Kasarvadavali, developingStatus, rapidly developing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developingStatus Context triple: [Kasarvadavali, developingStatus, rapidly developing]
-
A.
hasDevelopmentStatus
chosen
Indicates the current stage or condition of progress or completion that something is in.
-
B.
underDevelopment
Indicates that something is currently being created, improved, or worked on and is not yet in its final or completed state.
-
C.
developsDuring
Indicates that one process, condition, or characteristic comes into existence or forms over the course of a specified time period, phase, or event.
-
D.
mainDevelopmentPeriod
Indicates the primary time span during which the main development or formation of something took place.
-
E.
developmentPhaseName
Indicates the specific stage or phase name within a broader development process or lifecycle.
- 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 26, 2026, 9:11 p.m.