Triple
T22178519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venture Challenge |
E548107
|
entity |
| Predicate | targetProfile |
P127611
|
FINISHED |
| Object | high-growth potential ventures |
—
|
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: high-growth potential ventures | Statement: [Venture Challenge, targetProfile, high-growth potential ventures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetProfile Context triple: [Venture Challenge, targetProfile, high-growth potential ventures]
-
A.
targetMemberProfile
chosen
Indicates that one entity is the specific member profile that is the focus or destination of another entity’s action or reference.
-
B.
profileType
Indicates the specific category or role classification assigned to a profile within a system.
-
C.
participantProfile
Indicates that an entity serves as the profile or descriptive record associated with a particular participant in an event, activity, or process.
-
D.
usesProfile
Indicates that one entity employs, operates under, or is associated with a particular profile in performing its actions or functions.
-
E.
typicalHeadProfile
Indicates that an entity has a head shape or outline that conforms to a standard or commonly observed profile for its type.
- 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_69e11e3d53f88190a2b690e3f25bb062 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a6dd5a081908035e81c068d8d5a |
completed | April 28, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:34 p.m.