Triple
T12207673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fréchet Inception Distance |
E290874
|
entity |
| Predicate | featureLayer |
P103794
|
FINISHED |
| Object | Inception-v3 pool3 layer |
—
|
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: Inception-v3 pool3 layer | Statement: [Fréchet Inception Distance, featureLayer, Inception-v3 pool3 layer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featureLayer Context triple: [Fréchet Inception Distance, featureLayer, Inception-v3 pool3 layer]
-
A.
targetsLayer
Indicates that one entity is directed at, operates on, or is specifically intended to affect a particular layer within a layered structure or system.
-
B.
featureType
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
-
C.
formsFeature
Indicates that one entity constitutes or creates a characteristic, component, or distinguishing element of another entity.
-
D.
withinFeature
Indicates that one entity is spatially contained inside or lies entirely within the bounds of another feature.
-
E.
arealFeature
Indicates a relationship where something is characterized as a spatial or geographic feature occupying an area on a surface or map.
- F. None of above. chosen
Provenance (4 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d920e312708190b4aede2e21f5f697 |
completed | April 10, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69d91c3d669c81908eea7ad61122d275 |
completed | April 10, 2026, 3:50 p.m. |
| PDg | Predicate description generation | batch_69d920c3dc9881908c396a4ab34f4836 |
completed | April 10, 2026, 4:09 p.m. |
Created at: April 8, 2026, 9:51 p.m.