Triple
T29354213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Namboole |
E744392
|
entity |
| Predicate | constructionSupportFrom |
P179930
|
FINISHED |
| Object | People's Republic of China |
—
|
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: People's Republic of China | Statement: [Namboole, constructionSupportFrom, People's Republic of China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructionSupportFrom Context triple: [Namboole, constructionSupportFrom, People's Republic of China]
-
A.
constructionBase
Indicates that one entity serves as the foundational structure or base upon which another entity is constructed or built.
-
B.
constructionType
Indicates the specific method or style by which something is built or constructed.
-
C.
constructionMethod
Indicates the technique or process by which something is built, assembled, or created.
-
D.
constructionOrigin
Indicates the source, cause, or initiating factor from which a construction or building project originates.
-
E.
constructionUsed
Indicates that one entity was employed as a construction method, material, or component in creating or assembling another entity.
- F. None of above. chosen
Provenance (4 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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
| PDg | Predicate description generation | batch_69f72920c6208190aa4aba6cb6193109 |
completed | May 3, 2026, 10:53 a.m. |
Created at: April 28, 2026, 2:09 p.m.