Triple
T6011441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungry |
E133840
|
entity |
| Predicate | hasPrimaryInstrumentation |
P62771
|
FINISHED |
| Object | sample-based production |
—
|
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: sample-based production | Statement: [Hungry, hasPrimaryInstrumentation, sample-based production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryInstrumentation Context triple: [Hungry, hasPrimaryInstrumentation, sample-based production]
-
A.
hasTypeOfInstrumentation
chosen
Indicates that one entity uses, involves, or is characterized by a particular type of instrumentation.
-
B.
hasPrimaryRuntime
Indicates that an entity is associated with a main or default runtime environment it primarily uses or depends on.
-
C.
supportsDynamicInstrumentation
Indicates that an entity is capable of being instrumented or monitored at runtime without requiring recompilation or restart.
-
D.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
E.
hasPrimaryFunction
Indicates that one entity serves as the main or principal function or role of another entity.
- 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_69c0087361a48190905c6b55969852b8 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f5159bc8190a988293bbbb99d24 |
completed | March 22, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69c049e4daf4819099bf870dc700e0a2 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.