Triple
T27593928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilot |
E699844
|
entity |
| Predicate | receivesConfigurationFrom |
P136172
|
FINISHED |
| Object | Istio Galley (historically) |
—
|
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: Istio Galley (historically) | Statement: [Pilot, receivesConfigurationFrom, Istio Galley (historically)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesConfigurationFrom Context triple: [Pilot, receivesConfigurationFrom, Istio Galley (historically)]
-
A.
reconfiguredFrom
Indicates that one entity has been altered, adapted, or rearranged from a prior entity or configuration, such that the current form results from modifying the original.
-
B.
exportConfigurationFor
Indicates that one entity produces and outputs a configuration suitable for use by another specified entity.
-
C.
supportsConfigurationFromHost
chosen
Indicates that an entity can accept and operate using configuration settings provided by a host system.
-
D.
wasReconfiguredIn
Indicates that an entity underwent a change in its configuration or setup during a specified time or event.
-
E.
hasConfiguration
Indicates that an entity is associated with or defined by a particular configuration or setup.
- 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 2:06 p.m.