Triple
T6524543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Threads |
E151268
|
entity |
| Predicate | usesLoginSystem |
P31941
|
FINISHED |
| Object | Instagram account |
—
|
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: Instagram account | Statement: [Threads, usesLoginSystem, Instagram account]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLoginSystem Context triple: [Threads, usesLoginSystem, Instagram account]
-
A.
authenticationSystem
chosen
Indicates that an entity functions as or is associated with a system responsible for verifying identities and controlling access.
-
B.
anonymousLoginUsername
Indicates that a username is used specifically for logging in anonymously, without revealing the user's real identity.
-
C.
authenticationRequired
Indicates that access to a resource or operation is restricted and can only be performed by entities that have successfully authenticated.
-
D.
loginScope
Indicates the specific permissions, access range, or contextual boundaries under which a user or system is authenticated during a login session.
-
E.
supportsMultiuser
Indicates that the subject is capable of handling or enabling simultaneous use by multiple users.
- 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_69c687f522748190b3058405553cdabd |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ad9831f88190a2b64cf6bc8c9a11 |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:45 p.m.