Triple
T25808624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Modern Green Development Co. |
E650042
|
entity |
| Predicate | projectCharacteristic |
P65006
|
FINISHED |
| Object | sustainability-focused |
—
|
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: sustainability-focused | Statement: [Modern Green Development Co., projectCharacteristic, sustainability-focused]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectCharacteristic Context triple: [Modern Green Development Co., projectCharacteristic, sustainability-focused]
-
A.
projectCharacteristics
chosen
Indicates the defining features, qualities, or attributes that characterize a particular project.
-
B.
entityCharacteristic
Indicates that an entity possesses, exhibits, or is defined by a particular characteristic or attribute.
-
C.
productCharacteristic
Indicates that a product possesses, exhibits, or is defined by a specific characteristic or attribute.
-
D.
catalogCharacteristic
Indicates that a catalog has a specific characteristic or attribute associated with it.
-
E.
dataCharacteristic
Indicates that one entity specifies a property, attribute, or feature that characterizes a given piece of data.
- 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f600c2a7748190809b59109e476169 |
completed | May 2, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 7:07 a.m.