Triple
T30887385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YC-97B |
E786803
|
entity |
| Predicate | testFunction |
P43154
|
FINISHED |
| Object | evaluation of passenger cabin layout |
—
|
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: evaluation of passenger cabin layout | Statement: [YC-97B, testFunction, evaluation of passenger cabin layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testFunction Context triple: [YC-97B, testFunction, evaluation of passenger cabin layout]
-
A.
publicFunction
Indicates that a function or method is accessible from outside its defining scope, module, or class (i.e., it has public visibility).
-
B.
apiFunction
Indicates that one entity is a callable operation or method provided by an API that another entity can invoke to perform a specific task or retrieve data.
-
C.
actualFunction
Indicates that something serves as the real, operative function or role performed in practice, as opposed to a nominal or theoretical one.
-
D.
testingMethod
chosen
Indicates the procedure, technique, or approach used to perform a particular test or evaluation.
-
E.
typicalFunction
Indicates that something serves as the usual or characteristic function or role of an 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f692071d00819083948e17acfe2644 |
completed | May 3, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:49 p.m.