Triple
T26930223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jababeka Industrial Estate |
E678191
|
entity |
| Predicate | notableProjectOf |
P52042
|
FINISHED |
| Object | PT Jababeka Tbk |
—
|
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: PT Jababeka Tbk | Statement: [Jababeka Industrial Estate, notableProjectOf, PT Jababeka Tbk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableProjectOf Context triple: [Jababeka Industrial Estate, notableProjectOf, PT Jababeka Tbk]
-
A.
notableProjectFor
chosen
Indicates that a particular project is especially significant, prominent, or noteworthy for a given entity.
-
B.
notableProjectType
Indicates the type or category of a project for which an entity is particularly well-known or notable.
-
C.
notableProjectArea
Indicates that an entity has a significant or distinguished project specifically associated with a particular area or domain.
-
D.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
E.
notableProjectCountry
Indicates that a country is associated with a notable project undertaken by the subject.
- 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_69eeeb4cac908190a45956c2993d1cc2 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69ff48199b1c8190bb05872f8a4f4673 |
completed | May 9, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69ff4746b1cc8190854f70a124df7d04 |
completed | May 9, 2026, 2:40 p.m. |
Created at: April 27, 2026, 6:12 a.m.