Triple
T3747757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patria e Onore |
E81247
|
entity |
| Predicate | hasConjunction |
P51086
|
FINISHED |
| Object | e |
—
|
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: e | Statement: [Patria e Onore, hasConjunction, e]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConjunction Context triple: [Patria e Onore, hasConjunction, e]
-
A.
hasConjunctForms
Indicates that an entity is associated with one or more conjunct (combined or compound) forms of itself or related elements.
-
B.
hasCondition
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
-
C.
hasJunctionIn
Indicates that one entity contains or includes a junction located within the spatial or structural extent of another entity.
-
D.
hasComb
Indicates that an entity possesses or is equipped with a comb.
-
E.
hasCoupling
Indicates that two entities are linked or joined together in a way that allows them to interact, transfer, or coordinate motion, energy, or information.
- 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_69ad8b19b7b08190a6188804e99c53e9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb6ac5ac8190934ec1a6c887a8f5 |
completed | March 8, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69adc04adebc819088d7f36d0ac343a6 |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc1560c248190b07438d766880990 |
completed | March 8, 2026, 6:35 p.m. |
Created at: March 8, 2026, 3:35 p.m.