Triple
T2459100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Message From Earth |
E54488
|
entity |
| Predicate | isPublicParticipationProject |
P40633
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [A Message From Earth, isPublicParticipationProject, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPublicParticipationProject Context triple: [A Message From Earth, isPublicParticipationProject, true]
-
A.
isNonProfitProjectOf
Indicates that a project operates on a non-profit basis and is initiated, owned, or managed by the referenced entity.
-
B.
isPublicEvent
Indicates that an event is open and accessible to the general public rather than restricted to a private or limited audience.
-
C.
eligibleProject
Indicates that a project satisfies the required conditions or criteria to qualify for a particular status, process, or benefit.
-
D.
participationModel
Indicates how entities are involved in or contribute to an activity, process, or interaction.
-
E.
hasProject
Indicates that an entity is associated with or responsible for a particular project.
- 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_69ab49dee84c819096b50a0049c347ac |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd49c5aa081909ab4f726a458b77f |
completed | March 7, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69abd0b199488190aa381b36593ae1ac |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd49b5d2481908817aeb171e2bd61 |
completed | March 7, 2026, 7:32 a.m. |
Created at: March 6, 2026, 9:44 p.m.