Triple
T29246991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zorro II |
E741465
|
entity |
| Predicate | logicalDesignBasedOn |
P146314
|
FINISHED |
| Object | Autoconfig protocol |
—
|
NE NERFINISHED |
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: Autoconfig protocol | Statement: [Zorro II, logicalDesignBasedOn, Autoconfig protocol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: logicalDesignBasedOn Context triple: [Zorro II, logicalDesignBasedOn, Autoconfig protocol]
-
A.
basedOnDesignBy
Indicates that something is created, developed, or structured according to the design conceived or produced by a specified entity.
-
B.
structuralDesign
Indicates the relationship in which an entity is responsible for planning, organizing, or defining the structural configuration or framework of another entity.
-
C.
hasDesignRelationship
chosen
Indicates that there exists a design-based relationship or association between two entities, such as one influencing, constraining, or deriving from the design of the other.
-
D.
parallelDesignTo
Indicates that one design is parallel or analogous to another in structure, function, or conceptual approach.
-
E.
AESDesignBasis
Indicates that something serves as the foundational design criteria or reference framework for an AES (e.g., system, standard, or facility) against which its configuration, performance, and safety are defined and evaluated.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6648a17708190a2b19c610549b5e5 |
completed | May 2, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:33 p.m.