Triple
T15631844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KONEX |
E375832
|
entity |
| Predicate | listingRequirementFocus |
P48210
|
FINISHED |
| Object | early-stage companies |
—
|
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: early-stage companies | Statement: [KONEX, listingRequirementFocus, early-stage companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listingRequirementFocus Context triple: [KONEX, listingRequirementFocus, early-stage companies]
-
A.
locationRequirement
Indicates that a specific location or type of place is required or must be satisfied for an action, condition, or relationship to hold.
-
B.
bookingRequirement
Indicates that a particular condition, rule, or prerequisite must be satisfied in order to make or confirm a booking.
-
C.
listingCriterion
chosen
Indicates the rule or standard used to determine how items are selected, ordered, or displayed in a listing.
-
D.
typicalRequirement
Indicates that one entity is a standard or commonly expected prerequisite, condition, or necessity for another entity.
-
E.
evaluationRequirement
Indicates that one entity imposes or specifies conditions under which another entity must be assessed, tested, or evaluated.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eb536348190b93ed3c178d1ffb8 |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda868d4481908f4bce1c64d2902a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:14 a.m.