Triple
T27731335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.SerializableAttribute |
E697436
|
entity |
| Predicate | isMetadataOnly |
P163119
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [System.SerializableAttribute, isMetadataOnly, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMetadataOnly Context triple: [System.SerializableAttribute, isMetadataOnly, true]
-
A.
isReferenceOnly
Indicates that the associated item is intended solely for reference purposes and not for direct use, modification, or primary operation.
-
B.
isSingle
Indicates that an entity is not currently in a romantic relationship or legally married.
-
C.
isOnlyCurrentThat
Indicates that the subject is the sole entity that currently satisfies or holds the specified condition, with no other concurrent instances.
-
D.
hasRepresentationOnlyIn
Indicates that an entity is represented or manifested exclusively within a specified medium, context, or domain, and not outside of it.
-
E.
isSelective
Indicates that the relationship or action involves choosing or affecting only certain specific entities or options while excluding others based on particular criteria.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6369b658c8190bc6d697b9a4d5c03 |
completed | May 2, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 27, 2026, 3:11 p.m.