Triple
T4922101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W4 star-forming region |
E110488
|
entity |
| Predicate | hasPhysicalProcess |
P1410
|
FINISHED |
| Object | massive star formation |
—
|
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: massive star formation | Statement: [W4 star-forming region, hasPhysicalProcess, massive star formation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhysicalProcess Context triple: [W4 star-forming region, hasPhysicalProcess, massive star formation]
-
A.
hasPhysicalNature
Indicates that one entity possesses or exhibits a specific physical form, composition, or material nature in relation to another.
-
B.
hasProcess
chosen
Indicates that an entity is associated with, participates in, or is characterized by a particular process.
-
C.
hasPhysicalFootprint
Indicates that one entity occupies or affects a specific physical area or space in the real world.
-
D.
isPhysicalArtifact
Indicates that the subject is a tangible, man-made object that physically exists in the real world.
-
E.
hasPhotographicProcess
Indicates that something is associated with, created by, or characterized through a specific photographic process or technique.
- 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ffc2ab08190992db2400562bcee |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3421588190ab08e92b9558042e |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.