Triple
T27940547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galliano |
E700727
|
entity |
| Predicate | hasCoreCategory |
P82611
|
FINISHED |
| Object | runway collections |
—
|
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: runway collections | Statement: [Galliano, hasCoreCategory, runway collections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreCategory Context triple: [Galliano, hasCoreCategory, runway collections]
-
A.
hasCore
Indicates that one entity possesses, contains, or is built around a central or most essential component represented by another entity.
-
B.
hasCategories
chosen
Indicates that an entity is associated with one or more categories that classify or group it.
-
C.
hasCategorySystem
Indicates that an entity is associated with or organized according to a particular categorization system.
-
D.
hasCategoryOn
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
E.
hasCoreArea
Indicates that an entity possesses a primary or central area that is fundamental to its structure, function, or focus.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ff5b233e9c8190adc06cca0758986b |
completed | May 9, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69ff5a5682108190a006b23c4fcdcc7c |
completed | May 9, 2026, 4:01 p.m. |
Created at: April 27, 2026, 7:17 p.m.