Triple
T871383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GPT-3 |
E18819
|
entity |
| Predicate | fewShotPrompting |
P8562
|
FINISHED |
| Object | supported |
—
|
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: supported | Statement: [GPT-3, fewShotPrompting, supported]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fewShotPrompting Context triple: [GPT-3, fewShotPrompting, supported]
-
A.
coPilotWith
Indicates that two entities jointly serve as pilots or share piloting responsibilities for the same vehicle or mission.
-
B.
coPilotOf
Indicates that one entity serves as the co-pilot assisting and supporting another entity in operating or navigating a vehicle or craft.
-
C.
toolUseExamples
chosen
Indicates that one entity provides example instances or demonstrations of how a particular tool is or can be used by another entity.
-
D.
near
Indicates that one entity is located at a short distance from another entity in space or position.
-
E.
providedFor
Indicates that one entity supplies, furnishes, or makes something available to or on behalf of another entity for its use or benefit.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac96850881908a2d776685126137 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa89ca008190b50d061ac7fe19f9 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.