Triple
T37932759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QXP |
E946260
|
entity |
| Predicate | commonlyDistributedAs |
P9486
|
FINISHED |
| Object | project source file |
—
|
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: project source file | Statement: [QXP, commonlyDistributedAs, project source file]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyDistributedAs Context triple: [QXP, commonlyDistributedAs, project source file]
-
A.
distributesAs
Indicates that one entity allocates or hands out something (such as resources, items, or information) to multiple other entities according to some plan or rule.
-
B.
distributedAs
chosen
Indicates that something is allocated, delivered, or spread out according to a particular pattern, rule, or distribution scheme.
-
C.
intendedDistribution
Indicates the planned or expected way in which something is to be distributed among recipients or locations.
-
D.
hasDistributionForm
Indicates that an entity is associated with a particular physical or pharmaceutical form in which it is distributed or made available.
-
E.
hasCommunityDistribution
Indicates that something is associated with or occurs within a particular community or set of communities.
- 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff691f5ae481908597ce245188d31c |
completed | May 9, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69ff67ceeeb081909fd00cad166c4b6a |
completed | May 9, 2026, 4:58 p.m. |
Created at: May 3, 2026, 4:20 p.m.