Triple

T890840
Position Surface form Disambiguated ID Type / Status
Subject Fidelis E19233 entity
Predicate relatedNoun P10003 FINISHED
Object fides 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: fides | Statement: [Fidelis, relatedNoun, fides]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relatedNoun
Context triple: [Fidelis, relatedNoun, fides]
  • A. relatedTo
    Indicates a general, non-specific relationship or association exists between two entities.
  • B. semanticRelation
    Indicates a general meaning-based connection between two entities, such as similarity, implication, or conceptual association.
  • C. relatedField
    Indicates that one field, topic, or area of study is connected or relevant to another in subject matter or application.
  • D. linguisticallyRelatedTo chosen
    Indicates that two entities are connected through a linguistic relationship, such as sharing a common language, origin, structure, or other language-based association.
  • E. moreDistantlyRelatedTo
    Indicates that one entity is related to another by a more distant or indirect relationship compared to some closer reference relationship.
  • 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_69a4939d37188190848be3d426ebc9ae completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ad019e448190ab991e85dc6d7708 completed March 1, 2026, 9:17 p.m.
PD Predicate disambiguation batch_69a4aa9372e88190b5a9db4afdc045c6 completed March 1, 2026, 9:07 p.m.
Created at: March 1, 2026, 7:39 p.m.