Triple
T10623865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Independent Submission Stream |
E250271
|
entity |
| Predicate | allowsSubmissionBy |
P12578
|
FINISHED |
| Object | individuals |
—
|
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: individuals | Statement: [Independent Submission Stream, allowsSubmissionBy, individuals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsSubmissionBy Context triple: [Independent Submission Stream, allowsSubmissionBy, individuals]
-
A.
submissionBy
Indicates that one entity is the submitter or originator of a particular submission associated with another entity.
-
B.
allows
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
C.
acceptsSubmissionsFrom
chosen
Indicates that one entity receives and is willing to consider submissions (such as content, proposals, or applications) originating from another entity.
-
D.
approvedBy
Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
-
E.
hasSubmissionPolicy
Indicates that an entity is associated with a specific set of rules or conditions governing how submissions to it must be made.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df7f11fc8190aed858f2e1443c08 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 8:52 p.m.